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

Re: Subversion's Build System Issues (fwd)

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-09-24 20:47:23 CEST

On Wed, Sep 24, 2003 at 04:28:18PM +0300, Shlomi Fish wrote:
>
> This is an E-mail I sent to gstein about the build system. If anyone can
> also shed more light onto the subject, I would be grateful.

Didn't give me a lot of time to respond... :-)

>...
> The first is the issue of the "install = buildonly" target, in which we
> have to put programs that should be compiled by make, but not installed by
> "make install". This is intended for svn-push and for the minimal client
> and stuff like that.

I'd take Philip's(?) suggestion and call it 'contrib' instead of
buildonly. Also, I would not put those into the default build rule. These
are contributed programs, and many developers and *users* may not want
them built.

If you change it over to 'contrib', then a person can always do:

$ make contrib

>...
> The second issue is that of installing the Subversion pkgconfig.file.
> subversion.pc.in (or svn.pc.in - whatever) exists, and is compiled into
> subversion.pc by configure. It needs to be installed in the Subversion
> installation path, under /lib/pkgconfig/. How can this be achieved?

Hunh? We don't have a subversion.pc file. Should one be created, we'd
handle it similar to svn-config.

> Other than that, it seems Chia-Ling Kao has some problems in integrating
> the build of the Perl bindings into build.conf, and would need some help.
> I don't know too much more about it so please ask him.

Haven't seen that. Will look.

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 20:55:00 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.