Adapting svnstsw to use Subversion's build system

Hi all,

I have a few questions about Subversion's build system. I'm currently
trying to figure out how to adapt svnstsw (contrib/server-side/svnstsw)
to use Subversion's build system. I'm not familiar with how gen-make.py
works, and I'm concerned that adapting svnstsw will require substantial
changes -- either to Subversion's build system or to svnstsw code.

Here are my questions:

1. Is there a document detailing the semantics of build.conf?

2. svnstsw's current build system builds and installs an executable, a
library (and its corresponding public headers), some man pages, and some
Doxygen html API documentation (if 'make html' is run). Is all of this
possible with build.conf, or will I need to make some changes (either to
svnstsw or to gen-make.py)?

3. Is it safe to assume that svnserve will be installed to 'SVN_BINDIR
"/svnserve"'?

4. In general, is it OK to add files to AC_CONFIG_FILES in configure.ac
in order to support stuff in contrib?

5. In general, is it OK to add some .m4 files to build/ac-macros in
order to support stuff in contrib?

6. svnstsw makes heavy use of C99 features. Would it be OK to add the
AC_PROG_CC_C99 autoconf test to an .m4 file and only compile svnstsw if
'x${ac_cv_prog_cc_c99}' != 'xno'? Or is this too invasive?

7. The AC_PROG_CC_C99 autoconf test was introduced in autoconf 2.60,
but <http://subversion.tigris.org/release-process.html#before-release>
says that autoconf 2.59 should be used. Is this still valid?

8. How would I conditionally compile svnstsw (to skip
building/installing it if C99 support is not present)?

Thanks,
Richard

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-05 20:50:53 CEST