Re:Strengths, weaknesses, opportunities, and threats facing ...
by jcelerier on Monday May 02, 2022 @02:54AM
(#31232115)
But you only have to do this if you don't want to run an actual GUI or ncurses UI which does this for you for some reason ? What would you suggest instead ?
[ Parent
| on HN ]
Re:Strengths, weaknesses, opportunities, and threats facing ...
by cycomanic on Monday May 02, 2022 @03:37PM
(#31239803)
Why do I need to run a gui or ncurses UI if I just want to do the equivalent of
configure && make && make install?
Re:Strengths, weaknesses, opportunities, and threats facing ...
by jcelerier on Tuesday May 03, 2022 @01:34AM
(#31245007)
The equivalent of this is
cmake -S source_folder -B build_folder
cmake --build build_folder
cmake --install build_folder
You don't need to run a GUI at all for this, I don't see how you could infer this from the previous messages
Re:Strengths, weaknesses, opportunities, and threats facing ...
by tpush on Monday May 02, 2022 @05:15AM
(#31232801)
Something like 'cmake --list-options CMakeLists.txt' seems the most obvious.
Re:Strengths, weaknesses, opportunities, and threats facing ...
by jcelerier on Monday May 02, 2022 @08:50AM
(#31234466)
I don't think it would be meaningfully different from what you would get by doing
less CMakeCache.txt
Listing the options cannot be done by just introspecting a CMakeLists: what would it show for: if(FOO)
option(ENABLE_BAMBOOZLE_${FOO} "Enable Bamboozle - ${FOO}-specific version" OFF)
else()
option(ENABLE_BAMBOOZLE "Enable Bamboozle" ON)
endif()
(and if your meta-build system does not allow to do that, I'm sorry but I'll have to build a meta-meta-build-system on top of it which implements it and no one will like it)