| |
| |
On 3/4/21 9:48 PM duncan wrote:
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.
In 2008 this was indeed "state of the art", which means FLTK 1.1. I
don't know who wrote these early CMake files but I read recently that
someone used them even now to build FLTK 1.1.
FLTK 1.3 had just started development in 2008.
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?
If you can, it would be useful to annotate it; say it's outdated now
(i.e. usable for outdated FLTK 1.1), and refer users to the current
README.CMake.txt
Just don't duplicate (too much) information of README.CMake.txt - I'm
pretty sure this will change before we release 1.4.0.
--
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/a8d322b5-3f90-f9c0-968d-9c23ac827743%40online.de.
[ Direct Link to Message ] | |
|
| |
