Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Visual Studio style projects

Title: Visual Studio style projects
Hi Eric,
This is something we're working on as part of the e4 effort. We have had discussions in the CDT community on allowing projects to be more flexible. We've even done some prototyping using the Eclipse File System which is the later between IResource stuff and the actual file system that stores them in hopes of making the mapping more virtual if you will.
So I guess the short answer that there is work in progress but likely won't land until Eclipse 4.0 in a couple of years. We may look at productizing the EFS prototype to get some of this functionality sooner but in a kludgier way with CDT 5.1 next year.
At any rate, you aren't alone with this requirement. Also watch the platform-core-dev@xxxxxxxxxxx for progress since this is really more an Eclipse Platform thing than a CDT thing.


From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Eric Frey
Sent: Saturday, August 02, 2008 8:58 AM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Visual Studio style projects

I'm surprised I can't find more traffic about this on this mailing list, but I've got to adapt CDT to handle Visual Studio style projects, where the components of a project are explicitly defined in the project, files can live in any directory and multiple projects might live in the same directory, etc.  I'd really like to get the Project Explorer view to only list those files which are used in a project.

The link approach to including files from other directories won't work in our environment (for a variety of reasons) so that approach doesn't seem useful.

Has someone done this or something like it before?  Any quick suggestions as to how to go about it?  (If I had more time to do this, I'd love to try and make Project subclassable, but that would mean having a ProjectFactory, and that looks to be major surgery).



This email message is for the sole use of the intended recipient(s) and may contain confidential information.  Any unauthorized review, use, disclosure or distribution is prohibited.  If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

Back to the top