My observation about CL Compiler setup

CodeLite installation/troubleshooting forum
hbr_in
CodeLite Expert
Posts: 113
Joined: Fri Jul 11, 2008 9:12 am
Contact:

Re: My observation about CL Compiler setup

Post by hbr_in »

eranif wrote: Side note: Please dont write in CAPS
My Bad. I am really sorry. will not repeat.
eranif wrote:The compiler *always* starts from the project directory - and there is no way to change it.
OK i got it now.
eranif wrote: What will not happening? I was simply explained to you that the makeDirStep is not being called when executing target other than the 'all' target -

Code: Select all

"C:/cygwin/bin/make.EXE"  -j 1 -f "prj_bootloader.mk" type=Release C:/prj/sd_fat/testing/bootloader/prj/Release/command.o
since "C:/prj/sd_fat/testing/bootloader/prj" was my working directory & not prj directory, i said the previous command was not happening.
eranif wrote:this one is a bug in CL (which I already fixed in SVN)
I saw that. Thanks
eranif wrote:since he was never designed to do so.
Aren't compilers "SHE"
eranif wrote: The build process works like this:
cd to workspace directory - executes makefile
makefile: cd project directory
execute project makefile
The key word here is 'executed program' --> I was referring to the output of the build, (e.g. the executable)
Eran
Ok i got it now. sorry for all these mess. So basically working directory is where u put ur final executable program for debugging.

Reagrds
Gururaja
Post Reply