Re: [CMake] why no cumulative variable operations via the commandline?

Nicholas Braden wrote: > Ah, I understand now - I have a habit of forgetting that you can > configure existing CMake builds by repeatedly invoking cmake. I don't > know if such a feature exists but it definitely sounds useful. Yes, that would be another use case! R. -- Powered by

Re: [CMake] why no cumulative variable operations via the commandline?

Ah, I understand now - I have a habit of forgetting that you can configure existing CMake builds by repeatedly invoking cmake. I don't know if such a feature exists but it definitely sounds useful. On Sat, Mar 19, 2016 at 12:03 PM, René J. V. wrote: > Nicholas Braden wrote:

Re: [CMake] why no cumulative variable operations via the commandline?

Nicholas Braden wrote: > sense. Could you give an example of when you would find them useful? I > think maybe I am not understanding what you want. Yeah, I realise my explanation may not have been very clear. > If you just want to pass a list of values to a variable on the command > line,

Re: [CMake] why no cumulative variable operations via the commandline?

The command line is the first point where variables can be defined (all code runs after this), so I am not sure where you expect pre-existing values to come from in order for a += or -= to make sense. Could you give an example of when you would find them useful? I think maybe I am not

[CMake] why no cumulative variable operations via the commandline?

Hi, I've been wondering about something that is a real stumbling block in a build/distribution system like MacPorts where settings can be modified in any number of consecutive steps. For instance, depending on what dependencies a package ("port") requires and how those dependencies are