If the change to add
ISourceRoot means that all of a project's source files must be under a single
subdirectory of the project, or further complicates the issue of being able to
use source files outside of the project directory hierarchy, then I think it
is moving in the wrong direction.
Leo
======================================================================================
To:
cdt-core-dev@xxxxxxxxxxx
Date: Mon, 8 Mar
2004 12:24:54 -0500
(EST)
From: "Alain Magloire"
<alain@xxxxxxx>
Subject: [cdt-core-dev]
CDT Core Model API changes
Reply-To:
cdt-core-dev@xxxxxxxxxxx
Bonjour,
One of the problem
we have with the Core model, in term of resources
is scalability: finding
the binaries, finding the sources etc ...
Usually the users organize
by category, "src", "include", "objects", "icons",
"template"
The Core Model will spend
part of its time in irrelevant folders: "objects",
"icons",..
It would be nice if the
user could point to the correct directories.
For the Core, we would
like to make the following changes
+
ICModel
+----|ICProject
+---|ISourceRoot
+---|ICContainer
+---|ITranslationUnit
The ISourceRoot, is the
source browser/container, the equivalent of
IPackageFragmentRoot in
JDT.
for
example
prj1/
src/
icons/
objects/
If you set "prj1/src" to
be the source folder, ISourceRoot.
The other folders "icons",
"objects" will be ignore.
To be backward compatible,
the Project itself is the source root
when no other source
folders are define.
Relevant docs
:
(updated)
cdt-core-home/docs/qnx/cpathentry.html
cdt-core-home/docs/qnx/cmodel.html
(updated)
cdt-core-home/docs/binaryparser.html
cdt-core-home/docs/cdtproject_extension.html
--__--__--
_______________________________________________
cdt-core-dev mailing
list
cdt-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-core-dev
