Making parts of kdevelop optional

Hi,

I just stumbled across macro_optional_add_subdirectory,
should we use
that in KDevelop4 already? This would add a

BUILD_FOO

for each foo that we add, so its easier to disable teamwork,
designer,
svn, cvs or whatever else when compiling KDevelop4. For
example cvs
can't be excluded at all at the moment because it doesn't
have any
build-deps (same for make,qmake and cmake).

Of course we can do this later on, just wanted to get
opinions.

Andreas

-- 
Don't read everything you believe.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Thursday 24 May 2007 15:32, Andreas Pakulat wrote:
> Hi,
>
> I just stumbled across macro_optional_add_subdirectory,
should we use
> that in KDevelop4 already? This would add a
>
> BUILD_FOO
>
> for each foo that we add, so its easier to disable
teamwork, designer,
> svn, cvs or whatever else when compiling KDevelop4. For
example cvs
> can't be excluded at all at the moment because it
doesn't have any
> build-deps (same for make,qmake and cmake).
>
> Of course we can do this later on, just wanted to get
opinions.
>
> Andreas

We're not using this already? If we're not, then we need to
be.
-- 
Matt

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 24.05.07 15:40:54, Matt Rogers wrote:
> On Thursday 24 May 2007 15:32, Andreas Pakulat wrote:
> > Hi,
> >
> > I just stumbled across
macro_optional_add_subdirectory, should we use
> > that in KDevelop4 already? This would add a
> >
> > BUILD_FOO
> >
> > for each foo that we add, so its easier to disable
teamwork, designer,
> > svn, cvs or whatever else when compiling
KDevelop4. For example cvs
> > can't be excluded at all at the moment because it
doesn't have any
> > build-deps (same for make,qmake and cmake).
> >
> > Of course we can do this later on, just wanted to
get opinions.
> 
> We're not using this already? If we're not, then we
need to be.

Done.

Andreas

-- 
Your depth of comprehension may tend to make you lax in
worldly ways.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 24.05.07 15:40:54, Matt Rogers wrote:
> On Thursday 24 May 2007 15:32, Andreas Pakulat wrote:
> > Hi,
> >
> > I just stumbled across
macro_optional_add_subdirectory, should we use
> > that in KDevelop4 already? This would add a
> >
> > BUILD_FOO
> >
> > for each foo that we add, so its easier to disable
teamwork, designer,
> > svn, cvs or whatever else when compiling
KDevelop4. For example cvs
> > can't be excluded at all at the moment because it
doesn't have any
> > build-deps (same for make,qmake and cmake).
> >
> > Of course we can do this later on, just wanted to
get opinions.
> 
> We're not using this already? If we're not, then we
need to be.

Done.

Andreas

-- 
Your depth of comprehension may tend to make you lax in
worldly ways.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel