Howto get Workspace folder as Compiler variable

[h4mb4l4ng]

Hi all,

Is there anyway to reference to workspace folder as a variable for compiler (e.g. MinGW GCC) ?  I've just imported a complex solution from VS2K5E with 3,4 projects having multiple-level of sub folders.  These projects reference to one another to compile.  In VS2KE, there is $(SolutionDir) variable, we need the same thing in C::B.  Also, cannot use absolute path because each developer can store the workspace in their own space and commit work to SVN.

Work around solution are also welcome :-).

Many many thanks for a nice IDE.

Cheers.

[thomas]

There is no such thing.

However, if you compile your Code::Blocks from source, you can add this feature rather easily.

Edit macrosmanager.cpp, insert at line 180:
wxFilename wsfn(Manager::Get()->GetProjectManager()->GetWorkspace()->GetFilename());
macros[_T("WORKSPACE")] = wsfn.GetFullPath();
macros[_T("WORKSPACE_PATH")] = wsfn.GetPath();

(untested)

[h4mb4l4ng]

There is no such thing.

However, if you compile your Code::Blocks from source, you can add this feature rather easily.

Edit macrosmanager.cpp, insert at line 180:
wxFilename wsfn(Manager::Get()->GetProjectManager()->GetWorkspace()->GetFilename());
macros[_T("WORKSPACE")] = wsfn.GetFullPath();
macros[_T("WORKSPACE_PATH")] = wsfn.GetPath();

(untested)

Hmm, not a bad idea, but we can't public the source code to the world .

It's much better if C::B can import output of external scripts/programs as environment variables.

Thanks anyway.

[thomas]

Hmm, not a bad idea, but we can't public the source code to the world

You don't need to do that, it is already public.
You can just checkout the sources, apply the change as pointed out above, and compile Code::Blocks.

It's much better if C::B can import output of external scripts/programs as environment variables.

What makes you think it can't? It's not what you originally asked for, though.

You may want to look into backticks, if you want to insert the output of external programs, or script variable expansion, if you want to run scripts during variable expansion.