Page 1 of 1

Building a CodeLite workspace without CodeLite (makedir)

Posted: Fri Feb 05, 2010 11:46 am
by jdl
Hi,

Problem:
I'd like to hand over my completed CodeLite workspace based tool app (compiled with mingw) to another developer. Problem is you need CodeLite to build the workspace because the makefile depends on the "makedir" executable distributed with CodeLite. Is there a way to do this currently? Should I make a feature request for this (something like "CodeLite independent makefile"). Is this even a feasible request or are there other dependencies I don't know about?

Thanks.

Re: Building a CodeLite workspace without CodeLite (makedir)

Posted: Fri Feb 05, 2010 12:12 pm
by eranif
jdl wrote:Should I make a feature request for this (something like "CodeLite independent makefile")
Yes
jdl wrote:Is this even a feasible request or are there other dependencies I don't know about?
Very much feasible.



Eran

Re: Building a CodeLite workspace without CodeLite (makedir)

Posted: Fri Feb 05, 2010 1:28 pm
by eranif
Here is the solution I implemented in trunk:
- All references to 'makedir' are now by using the variable $(MakeDirCommand)
- The environment variables section was moved to be generated *after* the default makefile variables section.

With these 2 fixes, you can now:
- Define your own environment variable (from *whithin* codelite) named MakeDirCommand and set it to whatever you want
- Export the makefile (right click on the project and select 'Export')

When setting an environment variable of your own the makefile will use the environment variable rather than the default one
BTW: this is now true for the entire 'hard-wired' variables

Eran