I would love to see this feature.
When I have to program on M$ VS I use this directory structure a lot to do small test of some parts of my program. I prefer not having to configure a whole library for that, and is better (for me) to have a common directory.
That said, i think this is often not used in GNU projects.
--- On Thu, 12/11/08, Malcolm Lalkaka <mlalkaka gmail com> wrote:
From: Malcolm Lalkaka <mlalkaka gmail com>
Subject: Re: [Anjuta-list] Project directory structure
To: "Sébastien Granjoux" <seb sfo free fr>
Cc: anjuta-list lists sourceforge net
Date: Thursday, December 11, 2008, 7:55 PM
On Thu, 2008-12-11 at 21:55 +0100, Sébastien Granjoux wrote:
> > I reuse code
a lot.
> > In Windows Visual Studio, I can set up a structure like this:
> > Source/Common - contains the common reused code
> > Source/Projectname - contains code for the specific project
> > Where "Source" is the root of all my projects.
> > I can't seem to find any mention in the doc for this kind of
> structure.
> > Is it possible?
>
> I don't think it's possible.
>
> The project file should be in the same directory than Source with some
> mandatory files with fixed names like configure.ac and so on.
>
> I think the best way to do this, is to make a library with common code
> and use it in different project.
Yes, the best way to do this would be to make a library. Ideally,
though, a library should have some sort of logical coherence; and the
way you describe it, I'm assuming your Common directory is just bits and
piece of
random but useful code.)
If you don't want to go through the trouble of actually building a
library out of Common, and you're just using this for personal projects,
another thing you can try is using symbolic links from your project
directories into the common directory. However, this is not a good
solution if you intend on distributing your project.
In general, referencing files from another project like you are
intending to do can cause problems in the long run, regardless of what
IDE you use. This is because if you change the functionality of classes,
functions, etc, under the Common directory to suit the purposes of the
project you're currently working on, it will also affect -- and possibly
break -- the other projects.
I absolute best solution for this kind of thing is using a source
control system that supports branching well, like Subversion
(SVN).
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Anjuta-list mailing list
Anjuta-list lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/anjuta-list
|
