[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

what to build? (was: Subversion's Build System Issues)

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-09-24 21:00:29 CEST

On Wed, Sep 24, 2003 at 09:45:09PM +0300, Shlomi Fish wrote:
> On Wed, 24 Sep 2003, Files wrote:
>...
> > My two cents. I'm just feeling like configure.in is more for adding third party
> > libraries, and tools used FOR compilation. Not for generating executables.

Well... configure does decide *which* executable to build, based on what
can be found in the environment. e.g. you don't want to build svnadmin if
you don't have bdb.

>...
> The problem is that Makefile.in contains the following directive:
>
> local-all: @BUILD_RULES@ @SWIG_BUILD_RULES@
>
> Where BUILD_RULES and SWIG_BUILD_RULES are configure.in substitutions.
> Now, in configure.in, BUILD_RULES is defined statically. So if we want
> some other meta-target to be compiled during the local-all stage, we need
> to add it there.

Right. But we don't want contrib programs built by default.

Hmm. In fact, we may want to disable building the test programs by
default. When a user does a 'make && make install", they are not going to
need the test programs. When they say 'make check', then we should build
them...

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 24 21:04:38 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.