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

Re: svn commit: rev 6179 - in trunk: . build/ac-macros

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2003-06-11 08:18:18 CEST

--On Wednesday, June 11, 2003 8:00 AM +0200 Patrick Mayweg <mayweg@qint.de>

> What a frequency of reposts do you think is appropriate ? Daily, weekly or
> monthly ?

Personally, I recommend once every two weeks until you get a reply. I think
some other people here on dev@svn have advocated once a week. Circumstances
change enough with people every two weeks that I think it's a relatively safe
guide. That said, it still may take a few tries to reach someone especially
if it's a relatively arcane topic where there are relatively few eyes (i.e.
build system).

> abs_srcdir and abs_builddir are not known in svn-config. I could have
> introduced them to the svn-config but it would have work alone, because the
> syntax for variables in a shell script is different than for a Makefile.
> What is what svn-config was meant for ? I thought it meant to give you the
> include path and the libraries needed, when you want to build an
> appilication on top of the subversion libraries. If you take a subversion
> release tarball, you will get the abs_srcdir and the abs_builddir problem
> and the resulting Makefiles have to be edited manualy.

The problem is that svn-config is meant to work on installed copies of
Subversion. That means that it can not reference anything withing abs_srcdir
or abs_builddir as we can not assume that those still exist when svn-config is
finally invoked. So, my point is that those references to abs_srcdir whether
explicit via $(abs_srcdir) or expanded at configure-time via $abs_srcdir still
don't work.

svn-config doesn't work right now and isn't installed on purpose because it is
fundamentally broken if you use in-tree dependencies. If you don't use
in-tree dependencies, then it works just fine. But, your commit just attempts
to hide the problem rather than dealing with it. I'd really rather not do

> This is what I want to do. I just started with what I already had and
> adopted it just as an intermediate step. To integrate into the build
> systems, I have to understand them first. But since I have to process
> different kind of files (java source and class files) as the rest of
> subversion, it may mean a major extentsion to the buildsystems.

My point is that your 'intermediary' step introduces a bogus change into the
main build system.

> I did not had the time to try to understand the buildsystems. I also need to
> create the dsp and ?vcproj? files on windows.

Yup. That's why if you can integrate with the build.conf, you'll get those
for free. But, that's something that Greg has the most experience with.
You'll probably need some Python-fu in order to understand it.

> This is only the intermediate step, I will remove automake, when I
> intergrate with the build system.

Yup, but if you want the top-level configure script to produce the Makefile,
then it can't have any automake artifacts. I think that's the easiest
short-term solution available to you. If you have time later, then you can
figure out how to get it to work with build.conf.

> What is a pkg-config file ? Where do I find information about that ?

<http://www.freedesktop.org/software/pkgconfig/> -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 11 08:19:30 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.