Patches for $(ProjectWorkingDirectory) macro

[marfi]

Hi Eran,
I've added new macro called $(ProjectWorkingDirectory) expanding current project working directory to the external tools. Please, could you check it and add to the trunk if possible?

Best regards
Michal

[eranif]

Which working directory do you mean: the build working directory or the execution working directory?

When using a 'custom build' project the 'working directory' for the *build* is taken from the 'custom build' tab settings, while the working directory for execution is taken from the 'General' tab of the project settings

I think that the name of the macro should reflect this distinction.
Eran

[marfi]

I mean execution working directory taken from 'General' tab. I use it in external tools together with gprof and valgrind tools. Thanks to this macro I managed to integrate those validation tools with CL so now they work with any project. Btw, I created simple wrapper in wxPython for Gprof2Dot tool so now I'm able to create nice call graphs from information provided by gprof directly from CL So, what are your proposals for name of the new macro?

Regards
Michal

[marfi]

Hi Eran,
here are the modified patches we talked about at IRC.

Regards
Michal

[eranif]

I applied a modified version of the patch

Eran

[aprilmot]

Hello Mr.Michal,
I would like to use the tool you have mentioned below for my CPP learning . Is it possible for you share this wrapper.

Btw, I created simple wrapper in wxPython for Gprof2Dot tool so now I'm able to create nice call graphs from information provided by gprof directly from CL

Thank you in Advance.
Regards
Aprilmot