FLTK logo

Re: [fltk.coredev] Re: Understanding macOS build environments

FLTK matrix user chat room
(using Element browser app)   FLTK gitter user chat room   GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 All Forums  |  Back to fltk.coredev  ]
 
Previous Message ]New Message | Reply ]Next Message ]

Re: Re: Understanding macOS build environments duncan Mar 04, 2021  
 
AFAIC it's officially find_package(NAME options ...) which will
eventually call FindXXXX.cmake (which is called "module mode") or use
XXXXConfig.cmake (which is called "config mode"). See the CMake docs for
find_package(). The way you call it decides which option is chosen or if
you leave it to find_package() to choose - whatever it finds.

I've read through the CMake docs and a few other resources on this. 

Part of the CMake docs is the wiki page about "Using CMake to build an FLTK application"
which was "state of the art" and "limit of my knowledge" when I put it together in 2008 but
which is probably now contributing to the confusion. If I can still edit it[*], maybe it would be
useful to modify / annotate it to make it consistent with the current README.CMake.txt
build advice, no?

D.

[*] They moved it from its original location, so have the ownership/permissions changed?
https://gitlab.kitware.com/cmake/community/-/wikis/doc/tutorials/ForFLTK and
https://www.fltk.org/articles.php?L834
 
 

 

--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/4e68ed27-05bf-46d8-8f59-86cd9eb85327n%40googlegroups.com.
Direct Link to Message ]
 
     
Previous Message ]New Message | Reply ]Next Message ]
 
 

Comments are owned by the poster. All other content is copyright 1998-2024 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to 'erco@seriss.com'.