Eclipse Community Forums: C / C++ IDE (CDT) » Absolute path for include compiler options makes project not exportable

Help

Home

Home » Language IDEs » C / C++ IDE (CDT) » Absolute path for include compiler options makes project not exportable

Show: Today's Messages :: Show Polls :: Message Navigator

Absolute path for include compiler options makes project not exportable [message #156133]

Thu, 13 October 2005 10:54

Jerome Correnoz

Messages: 80
Registered: July 2009

Member

Hi,

When specifying a library or include path in the compiler options,the
associated path is stored as an absolute path in the Build project file
(.cdtbuild).

This makes the project not exportable from one machine to another because
the path
are wrong on the other machine. Should be a relative path.

Is there a way to do it ? Is there already a bugzilla for it ?

Regards,
Jerome

Report message to a moderator

Re: Absolute path for include compiler options makes project not exportable [message #157225 is a reply to message #156133]

Wed, 02 November 2005 04:47

Eclipse User

Originally posted by: crecoskie.ti.com

Use a macro to specify the directories in which the files live, then
define that macro on each system on which you are going to build.

E.g. ${myMacro}/include

Chris

Jerome Correnoz wrote:

> Hi,

> When specifying a library or include path in the compiler options,the
> associated path is stored as an absolute path in the Build project file
> (.cdtbuild).

> This makes the project not exportable from one machine to another because
> the path
> are wrong on the other machine. Should be a relative path.

> Is there a way to do it ? Is there already a bugzilla for it ?

> Regards,
> Jerome

Report message to a moderator

Previous Topic:	Finding commnets using CDT parser
Next Topic:	extending CDT new project wizard

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Jun 27 20:55:42 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter