[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [cdt-dev] Change in default include paths
|
Hi Mike,
At the moment the process is not expanding
macros that come from outside template macros. The macros list doesn't
include environment variables. Anything that defines with "$()",
It will compare with already available list of macros and throw an error
if it can't find them. I can think of two possible solutions to your problem:
1. Create your own process similar to
the AppendToMBSStringListValues that will look for macros in the environment
as well. Look into 'SimpleMakeFileGenerator' for more details on how DougS
solved the makefile macros and tempalte macros conflict issue.
2. Raise a defect to add environment
variables to the template engine macros list by default. Then we can discuss
about what are all should be added to the macros list under the same defect..
Regards,
-Bala
"Mike Wrighton"
<mikew@xxxxxxxxxxxxxx>
Sent by: cdt-dev-bounces@xxxxxxxxxxx
17/07/2007 17:08
Please respond to
"CDT General developers list." <cdt-dev@xxxxxxxxxxx> |
|
To
| "CDT General developers list."
<cdt-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| RE: [cdt-dev] Change in default include
paths |
|
This is great except it can’t
seem to expand macros, and really I’d like to get the extra paths from
an environment variable rather than hard-code them which is a bit nasty.
The code I tried was:
<process type="org.eclipse.cdt.managedbuilder.core.AppendToMBSStringListOptionValues">
<simple name="projectName" value= "$(projectName)"/>
<complex-array name="resourcePaths">
<element>
<simple name="id" value="gnu.c.compiler.option.include.paths"
/>
<simple-array name="values">
<element value="$(env_var:CSINC)"
/>
</simple-array>
<simple name="path" value=""
/>
</element>
</complex-array>
</process>
This throws up an error when
I try to create a new project about an unexpandable macro?
Mike
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of bala.torati@xxxxxxxxxxx
Sent: 17 July 2007 16:18
To: CDT General developers list.
Subject: RE: [cdt-dev] Change in default include paths
You can use 'AppendToMBSStringListOptionValues'
process to append include paths. This template engine process can be used
to append to different MBS list values such as a String List, Include Paths,
Preprocessor Symbols, Libraries, Objects.
Regards,
-Bala
"Mike Wrighton"
<mikew@xxxxxxxxxxxxxx>
Sent by: cdt-dev-bounces@xxxxxxxxxxx
17/07/2007 16:01
Please respond to
"CDT General developers list." <cdt-dev@xxxxxxxxxxx> |
|
To
| "CDT General developers
list." <cdt-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| RE: [cdt-dev] Change in default include
paths |
|
This is something I’m after as well. I checked the ISV docs for templates
but all I can find are template processes to create new include folders,
and processes to link files to the project – I cant find anything which
actually appends the default include path?
Cheers,
Mike
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Doug Schaefer
Sent: 09 July 2007 15:47
To: CDT General developers list.
Subject: RE: [cdt-dev] Change in default include paths
These paths are coming from gcc itself. The scanner discovery feature asks
it for it’s built-ins and that’s what we’re getting.
If you have paths that aren’t gcc defaults that you’d like to add, I’d
recommend creating a project template that would add in those paths for
you. Documentation for that is in the ISV docs and you can look at our
built-in HelloWorld templates as examples.
Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, http://cdtdoug.blogspot.com
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Sheldon Dsouza
Sent: Monday, July 09, 2007 10:05 AM
To: CDT General developers list.
Subject: [cdt-dev] Change in default include paths
Hi,
When a C project is created in CDT,
the following default system include paths /usr/local, /usr/local/include
etc are added to the project properties. I need to modify these include
paths for my project creation, how do i go about this and which are the
source files that i have to change.
Regards,
Sheldon_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
**********************************************************************
Symbian Software Ltd is a company registered in England and Wales with
registered number 4190020 and registered office at 2-6 Boundary Row, Southwark,
London, SE1 8HP, UK. This message is intended only for use by the named
addressee and may contain privileged and/or confidential information. If
you are not the named addressee you should not disseminate, copy or take
any action in reliance on it. If you have received this message in error
please notify postmaster@xxxxxxxxxxx and delete the message and any attachments
accompanying it immediately. Neither Symbian nor any of its Affiliates
accepts liability for any corruption, interception, amendment, tampering
or viruses occurring to this message in transit or for any message sent
by its employees which is not in compliance with Symbian corporate policy.
**********************************************************************
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
********************************************************************** Symbian Software Ltd is a company registered in England and Wales with registered number 4190020 and registered office at 2-6 Boundary Row, Southwark, London, SE1 8HP, UK. This message is intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify postmaster@xxxxxxxxxxx and delete the message and any attachments accompanying it immediately. Neither Symbian nor any of its Affiliates accepts liability for any corruption, interception, amendment, tampering or viruses occurring to this message in transit or for any message sent by its employees which is not in compliance with Symbian corporate policy. **********************************************************************