James K. Lowden wrote on Thu, Aug 08, 2013 at 22:25:08 -0400:
> Stefan Sperling <stsp_at_elego.de> wrote:
> > If you manage to generate both the compiled-in strings and the man
> > pages (on UNIX only) from the same source format during the build,
> > I"m happy with that. If you manage to generate man pages from
> > 'svn help' output during the build process on UNIX, then I'm happy,
> > too.
>
> It sounds like we have agreement and the ball is back in my court. If
> there are no objections, I'll work on the following as a next step:
>
> 1. Get the sources for 1.9
> 2. Examine svn_cl__cmd_table
> 3. Prepare a doc build tree that creates two things:
> a. man pages
> b. plain text for --help, one file per subcommand
>
> The plain text filenames will have the extension ".in", so a
> simple Makefile rule can convert them to ".h" for inclusion into the
> appropriate source module.
You'd have to figure out something for windows as well, since we don't
use make that on that platform. (Several of our dependencies do, but we
just generate Visual Studio projects.)
In general, it'll be best if you hook into the existing build system ---
configure.ac, gen-make.py, and build.conf. The latter two are used on
all platforms (on unix they generate build-outputs.mk).
It would probably be worthwhile to familiarize yourself with the build
system on all platforms. Have a look at where translate_sql.py is
invoked from. (It's invoked at autogen.sh time on unix, by the way,
meaning end-users don't need to have Python to build + install
Subversion from a tarball.)
Received on 2013-08-09 10:21:59 CEST