| |
| |
On 3/3/21 1:34 PM 'MacArthur, Ian (Leonardo, UK)' via fltk.coredev wrote:
This reply is going off-topic a bit, but:
Is there a difference between fltk-config generated by configure vs CMake?
Under mingw, there is - but I wonder if this is a more generic issue?
Yes, I think it's not only MinGW.
In particular the "--optim" options are not set in the cmake generated file, but are set in the autoconf generated file.
But... I do wonder if all of the cmake build is ignoring the optim settings anyway, so what is in the fltk-config does match how the lib was actually built (but not how we wanted the lib to be built, in essence.)
I can tell you that the CMake builds honor the "OPTION_OPTIM" flags in
the build, I'm often using this option in cmake-gui to add compiler
flags like "-Wno-deprecated-declarations" and others. This works fine.
The OPTION_OPTIM flags are however not initially populated by our CMake
build files as the equivalent flags are in configure (with flags related
to debugging or not). In CMake there are other means (for instance
CMAKE_CXX_FLAGS[_config] where '_config' can be '_Debug' etc.) to set
the compiler debug or no-debug flags, respectively.
That said, we need a way to "export" these or equivalent debug flags to
fltk-config which is supposedly the only missing point here. It's just
not done right now.
Sorry, I think you asked this already but I never came to doing it. I
should. Please remind me again later or open a GitHub Issue, maybe...
--
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/da0a9003-3abf-3c46-551c-c18719f56e83%40online.de.
[ Direct Link to Message ] | |
|
| |
