Well, given that the process has access to
all of the Eclipse and CDT APIs, I’m sure you could find a way.
At any rate, that does bring to mind
something that’s bothered me. I’m not sure the workflow of the new
project wizard is correct, and am interested to see of others think the same.
When creating a new project, what I think
I want to do is select the toolchain first, then the project type, then the
template. Different toolchains support specific project types and specific
templates. I’m coming at this from a cross-platform perspective, where
the first thing you pick is what platforms you want to build your application
for, and that drives what toolchains you’d use.
So I’d like to see the toolchain and
project type panes flipped, and the contents of the project types pane reflect
the selected toolchains.
What I want to avoid is the user picking a
template and getting confused as to why his toolchain isn’t there. I’d
rather they’d select the toolchain and then see what templates are
available for that toolchain.
I’ve created https://bugs.eclipse.org/bugs/show_bug.cgi?id=197802.
Feel free to add your comments there.
Cheers,
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Mike Wrighton
Sent: Wednesday, July 25, 2007 10:00
AM
To: CDT
General developers list.
Subject: RE: [cdt-dev] API for
changing contents of template
Except, it would seem, create a new
project that uses a different toolchain??
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Doug Schaefer
Sent: 25 July 2007 14:58
To: CDT
General developers list.
Subject: RE: [cdt-dev] API for
changing contents of template
Yes. I think the real power of the
template engine is the template processes. You can do pretty much anything with
them.
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Mike Wrighton
Sent: Wednesday, July 25, 2007
7:26 AM
To: CDT
General developers list.
Subject: RE: [cdt-dev] API for
changing contents of template
Yeah exactly (as far as I know).
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sheldon Dsouza
Sent: 25 July 2007 12:12
To: CDT
General developers list.
Subject: Re: [cdt-dev] API for
changing contents of template
Thanks, so in order to do
this i will have to implement a process similar to
AppendToMBSStringListOptionValues to add my include paths.
Regards,
Sheldon
On 7/25/07, Mike
Wrighton <mikew@xxxxxxxxxxxxxx>
wrote:
Sheldon, I think what you need to do is create a template
process, and set the project options such as paths accordingly inside this
process. This is what I've done – I just call System.getEnv() inside my
template process to set the include and library paths based on environment
variables.
Hi,
Just wanted to know if it is
possible to modify the template XML before creating a project using API. As per
my previous question on adding include paths through the templates, the
includes paths needed for our projects are dependent on a particular target. So
if i select a particular target for project creation the include path will
change
e.g /target/usr/include this cannot be hard coded in the template. Needs to be
changed on the fly while creating the project.
Regards,
Sheldon
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev