You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently tried using --define CMAKE_BUILD_TYPE=Debug on the cget build command line for a simple local project/package, but discovered the resulting binary still had no debug symbols.
After investigation using the --verbose flag I realised that my custom define was propogating to the resulting cmake command line, the problem was that the default -DCMAKE_BUILD_TYPE=Release flag was also being added to the command line after my define and essentially replacing it.
Is it worth considering a change whereby the user's custom commandline defines are always added to the end of the resulting cmake command and thereby always taking precedence?
(This certainly seems like it'd fix my issue of not being able to enable Debug builds on my project, but I don't know if there'd be any other unwanted side-effects...?)
Thanks!
The text was updated successfully, but these errors were encountered:
Hi,
I recently tried using
--define CMAKE_BUILD_TYPE=Debug
on thecget build
command line for a simple local project/package, but discovered the resulting binary still had no debug symbols.After investigation using the
--verbose
flag I realised that my custom define was propogating to the resultingcmake
command line, the problem was that the default-DCMAKE_BUILD_TYPE=Release
flag was also being added to the command line after my define and essentially replacing it.Is it worth considering a change whereby the user's custom commandline defines are always added to the end of the resulting
cmake
command and thereby always taking precedence?(This certainly seems like it'd fix my issue of not being able to enable Debug builds on my project, but I don't know if there'd be any other unwanted side-effects...?)
Thanks!
The text was updated successfully, but these errors were encountered: