Setting Environment Variables per project?
Posted: Wed Jun 29, 2011 5:22 am
If I understand correctly:
Say on Windows, the default environment variable has WXCFG=gcc_dll\mswu. So for debug versions one should create a new set with WXCFG=gcc_dll\mswud and set the debug configuration environment set of the project to the newly created one.
On the same basis, under Mac one can create a new set with WX_TOOL=/path/to/wx/build/wx-config and then set the project environment to this set.
However, if one then takes the workspace to another machine (or distributes the workspace) there's a need to rec-create the global environments sets and change the project configuration environment.
If all this is right, would it not be wise to simply have under Project Settings > Environment (and probably also Workspace Settings) a box that allows adding additional environment variables? It seems very obvious to me that some environment variable are truly global (the location of codelite, for example), while others are specific per project/workspace.
Does this make sense?
Say on Windows, the default environment variable has WXCFG=gcc_dll\mswu. So for debug versions one should create a new set with WXCFG=gcc_dll\mswud and set the debug configuration environment set of the project to the newly created one.
On the same basis, under Mac one can create a new set with WX_TOOL=/path/to/wx/build/wx-config and then set the project environment to this set.
However, if one then takes the workspace to another machine (or distributes the workspace) there's a need to rec-create the global environments sets and change the project configuration environment.
If all this is right, would it not be wise to simply have under Project Settings > Environment (and probably also Workspace Settings) a box that allows adding additional environment variables? It seems very obvious to me that some environment variable are truly global (the location of codelite, for example), while others are specific per project/workspace.
Does this make sense?