Re: [CMake] setting/removing compiler flag (-g) for a single project directory

2017-09-16 Thread Steven Velez
Gotcha... yeah target definitions are available globally, in all directories after they are defined (source order is important). I had never thought of this as a global variable or constant, but I guess in a way it is. In that way, then I would think it is a sort of special case... but I

Re: [CMake] setting/removing compiler flag (-g) for a single project directory

2017-09-16 Thread René J . V . Bertin
On Friday September 15 2017 16:51:24 Steven Velez wrote: >Yeah... I didn't mean to respond personally... i didn't realize my client >was doing that and not the list. OK, replying back to the list then. >What do you mean by "variables related to targets have global scope"? I probably could have

[CMake] setting/removing compiler flag (-g) for a single project directory

2017-09-15 Thread René J . V . Bertin
Hi, Is it possible to set and/or remove compiler arguments on a project subdirectory that holds a tree with sources of a considerable number of build targets? An example to make this more concrete: I have a project that contains common_libs plugins/foo plugins/this_one I'm just interested