Skip to main content



      Home
Home » Language IDEs » C / C++ IDE (CDT) » project concept suggestion
project concept suggestion [message #101777] Fri, 07 May 2004 17:54 Go to next message
Eclipse UserFriend
Originally posted by: tom.hilinski.comcast.net

I would like to make a suggestion for extending the kind of projects
available for CDT.

The 2 types (standard and mangaged) are not flexible enough for targets
with complex builds. For instance, if the source files come from several
directories, not all of which share a root, then we would like to be able
to specify source files from any directory to be included in the build,
irrespective of what CDT thinks is the root location.

Example tree:

tree1
|--- src
|--- classesA
|--- classesB
tree2
|--- src
|--- classesC
|--- classesD

A build may want classes from each of these class directories, but not all
classes from any directory. And tree1 and tree2 may not necessarily share
a nearby root.

Also, I would not want the CDT project files to be in either tree1 or
tree2. In our case, we have a separate directory w/project subdirs to
contain the many targets and compilers. For consistency, we need all the
CDT project files to go there. For example:

projects
|--- gcc-linux
|--- gcc-solaris
|--- eclipse (CDT project files here)

Lastly, having any CDT project files in the eclipse workspace prevents the
source tree from being packaged w/all necessary project and configuration
files. All project files should be allowed to stay together in a
user-specified location. A user may have their eclipse workspace in a
different location, and so a simple extraction from the package (e.g., tar
or zip file) will not work.

These concepts of a project work for makefiles and for all other common
IDEs (Microsoft, Borland, some sourceforge IDEs I've looked at). Has there
been any discussion of or plans to provide CDT with this type of project
capability?
Re: project concept suggestion [message #101925 is a reply to message #101777] Mon, 10 May 2004 14:30 Go to previous messageGo to next message
Eclipse UserFriend
Tom Hilinski wrote:

> I would like to make a suggestion for extending the kind of projects
> available for CDT.
>
> The 2 types (standard and mangaged) are not flexible enough for targets
> with complex builds. For instance, if the source files come from several
> directories, not all of which share a root, then we would like to be able
> to specify source files from any directory to be included in the build,
> irrespective of what CDT thinks is the root location.
>

Couldn't you simply use symbolic links to link the other locations into
CDT's project root? like,

$ ln -s ~/some/location ~/eclipse/workspace/some_project/some_location

(assuming you are on a UNIX or UNIX-like platform of course).


/Jesper Juhl
Re: project concept suggestion [message #101975 is a reply to message #101925] Tue, 11 May 2004 11:26 Go to previous message
Eclipse UserFriend
Originally posted by: tom.hilinski.comcast.net

> Couldn't you simply use symbolic links to link the other locations into
> CDT's project root? like,

> $ ln -s ~/some/location ~/eclipse/workspace/some_project/some_location

> (assuming you are on a UNIX or UNIX-like platform of course).


> /Jesper Juhl

We work on several platforms, Windows, Linux clusters, solaris, and, are
planning for grid computing in the next several months. So, we need
several build configurations, and all must be easily "packaged", i.e., all
source and build files checked into CVS, as well as tar-able.
Previous Topic:100% proc use :/
Next Topic:Parser not recognize symbols defined in another file
Goto Forum:
  


Current Time: Mon Jul 14 09:06:12 EDT 2025

Powered by FUDForum. Page generated in 0.06595 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top