Mariusz Matuszek

... and this one was me adjusting LOD ranges in flight. It happened right after closing the LOD adjustment menu.

Maybe I'll add two recent backtraces then. The first one happened when 'just flying', during a turn, when some new scenery had to be shown.

Testing... Edit: command ../fgmeta/download_and_compile.sh -s --cleanup -pn -j8 --cmake-arg ALL=-DCMAKE_EXPORT_COMPILE_COMMANDS=YES FGFS OSG SIMGEAR worked as expected. All compile_commands.json files were created as requested. Thank you very much again.

Testing...

I agree about the order, so component-specific options can override the global ones. The option to aggregate multiple cmake arguments in a single --cmake-args option seems interesting too, although I personally do not set that many options, so to me the current method (augmented with the 'ALL' option) would be sufficient. Could a comma be used as an argument list separator, instead of a space? I do not recall any cmake arguments using commas off the top of my head.. As for deciding between: --cmake_arg...

I agree about the order, so component-specific options can override the global ones. The option to aggregate multiple cmake arguments in a single --cmake-args option seems interesting too, although I personally do not set that many options, so to me the current method (augmented with the 'ALL' option) would be sufficient. Could a comma be used as an argument list separator, instead of a space? I do not recall any cmake arguments using commas off the top of my head.. As for deciding between: --cmake_arg...

Looking at the way you modified the d_and_c I was thinking about adding a phony component ALL to the CMAKE_BASED_COMPONENTS list and then, in every component-specific cmake invocation, like, for example $extra "${FGFS_CMAKE_ARGS[@]}" \ append $extra "${ALL_CMAKE_ARGS[@]}" So together that part of cmake call would look like this (fgfs in example): ... $extra "${FGFS_CMAKE_ARGS[@]}" \ $extra "${ALL_CMAKE_ARGS[@]}" \ ../../flightgear 2>&1 | _logOutput Would this make sense? It looks like your logic...

Arrgh! gotta love it, when editor 'knows better' and there is no edit option :( Anyway, example use was meant to look like d_and_c "other options" --cmake-option=ALL="some cmake option" "components to build" Sorry for the noise.