absolute paths in make files... again

[elkvis]

I tried the solution suggested in this thread: http://forums.codelite.org/viewtopic.php?f=11&t=1449

but it did not solve my problem. all of my file types now use "$(FilePath)$(FileFullName)" in their compilation template, but it is still generating makefiles with absolute paths. since my dev environment and my live environment have slightly different configurations, this will not work. I have even checked my .codelite/config/build_settings.xml file, and verified that all instances of $(FileFullPath) have been replaced with the proper value.

[elkvis]

does anyone have any suggestions for this? I'm out of ideas.

[eranif]

You can not completely remove the full paths from the makefile.
It requires some code changes to be able to do this

Another alternative (an idea I have been playing around for some time now) is providing a standalone command line tool that accepts as input the project file.

Eran

[elkvis]

what is the purpose of using absolute paths? it makes more sense, to me, to use paths relative to the workspace.

[eranif]

what is the purpose of using absolute paths? it makes more sense, to me, to use paths relative to the workspace.

The Makefile were not intended to be portable. The workspace / project were designed to be portable.

codelite is not a makefile generator it uses makefile as a tool for building the project. The project / workspace are the parts that are meant to be portable (and they are) and should be used on different machines.

Why don't you install another codelite on the second machine ?

FYI:
In earlier versions of gdb, (6.5-) using absolute paths fixed some problems with placing breakpoints in the source code.

Eran

[elkvis]

I have codelite installed on the other machines, but logging in to X on a remote linux machine, via NX, just to build code that can easily be built from the command line, incurs an unnecessary load on the system, which has better things to do, like build the code or continue to run the live production system.