Code::Blocks Forums
Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: killerbot on April 24, 2013, 10:57:24 pm
-
Hi,
It has been already proposed to give the workspaces more power, what do you think of the following :
- compiler options/defines on the workspace ==> applies to every project in the workspace (has already been mentioned)
- grouping of projects (aka like virtual folders), so project A, D, H go together in some group, and project B, O,P in some other group. Where the grouping makes some sense to the user, this grouping should then also be visible in the project tree
-
I had plans on working on this, bug got sidetracked by the ui stuff. :(
-
http://idioms.thefreedictionary.com/on+steroids
"on steroids" means: in a much more powerful or extreme form :)
- compiler options/defines on the workspace ==> applies to every project in the workspace (has already been mentioned)
I love this feature. Is it related to some discussion of using some global variables (GCV, like -O2, -g...)?
-
- compiler options/defines on the workspace ==> applies to every project in the workspace (has already been mentioned)
- grouping of projects (aka like virtual folders), so project A, D, H go together in some group, and project B, O,P in some other group. Where the grouping makes some sense to the user, this grouping should then also be visible in the project tree
For the first: Yes.
For the second: What would be a use-case?
-
For the second: What would be a use-case?
To group related projects, like one group for libraries, one group for plugins, etc.