I'm pretty sure you want to be looking at build.conf instead.
configure.in really shouldn't need to change, because:
* build-outputs.mk is pulled in by Makefile, which contains all targets
based on build.conf.
* configure.in manages configuration rules for generating the Makefile.
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.
Shamim Islam
BA BS
Shlomi Fish (shlomif@vipe.technion.ac.il) 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.
>
>Regards,
>
> Shlomi Fish
>
>
>----------------------------------------------------------------------
>Shlomi Fish shlomif@vipe.technion.ac.il
>Home Page: http://t2.technion.ac.il/~shlomif/
>
>An apple a day will keep a doctor away. Two apples a day will keep two
>doctors away.
>
> Falk Fish
>---------- Forwarded message ----------
>Date: Wed, 24 Sep 2003 10:01:50 +0300 (IDT)
>From: Shlomi Fish <shlomif@vipe.technion.ac.il>
>To: Greg Stein <gstein@lyra.org>
>Cc: Ben Collins-Sussman <sussman@collab.net>
>Subject: Subversion's Build System Issues
>
>
>Hi Greg!
>
>There are several patches that require interaction with the build system,
>whose issues with it need to be resolved. I was told you have
>originated it, and so I'm asking you what is the best way to resolve them.
>
>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.
>
>At the moment, the best resolution I could find from my understanding of
>the build system was to add buildonly in the appropriate place to
>configure.in:
>
><<<
>Index: configure.in
>===================================================================
>--- configure.in (revision 7099)
>+++ configure.in (working copy)
>@@ -256,9 +256,9 @@
> # Only add *_APACHE_RULE if we also have db, since mod_dav_svn depends on
>it.
> INSTALL_STATIC_RULES="install-bin install-docs"
> INSTALL_RULES="install-base-lib install-lib install-include
>install-static"
>-BUILD_RULES="base-lib lib bin test"
>+BUILD_RULES="base-lib lib bin buildonly test"
> if test "$svn_lib_berkeley_db" = "yes"; then
>- BUILD_RULES="base-lib fs-lib lib bin fs-bin $BUILD_APACHE_RULE test
>fs-test"
>+ BUILD_RULES="base-lib fs-lib lib bin buildonly fs-bin
>$BUILD_APACHE_RULE test fs-test"
> INSTALL_STATIC_RULES="install-bin install-fs-bin install-docs"
> INSTALL_RULES="install-base-lib install-fs-lib install-lib
>install-include install-static $INSTALL_APACHE_RULE"
> FS_TEST_DEPS="\$(FS_TEST_DEPS)"
>>>>
>
>Is there a better way?
>
>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?
>
>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.
>
>Thanks in advance,
>
> Shlomi Fish
>
>
>
>----------------------------------------------------------------------
>Shlomi Fish shlomif@vipe.technion.ac.il
>Home Page: http://t2.technion.ac.il/~shlomif/
>
>An apple a day will keep a doctor away. Two apples a day will keep two
>doctors away.
>
> Falk Fish
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: dev-help@subversion.tigris.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:30:53 2003