(sorry for the delay) Gabriela Gibson wrote on Mon, Feb 18, 2013 at 12:10:50 +0000: > 2. Example compile > ------------------ > > svn co https://svn.apache.org/repos/asf/subversion/trunk > cd trunk > ./get-deps.sh
Note that the serf this downloads must be compiled/installed (and potentially passed to configure) manually. > 5. Adding components to the build system > ------------------------------------------ > > The following sections step through making minimal additions to the > build system, the examples presents comprise a librabry, a minimal > execturable and a 3rd party package. > > 7. Adding an executable > ------------------------ > > The C files which comprise a stand-alone application: > How about just linking to a revnum wherein a standalone application was added? That's less likely to get out of date. For example % svn log -qv -l1 -r 1:HEAD subversion/tests/cmdline/atomic-ra-revprop-change.c ------------------------------------------------------------------------ r965054 | danielsh | 2010-07-17 14:23:38 +0300 (Sat, 17 Jul 2010) Changed paths: M /subversion/branches/atomic-revprop/build.conf M /subversion/branches/atomic-revprop/subversion/tests/cmdline A /subversion/branches/atomic-revprop/subversion/tests/cmdline/atomic-ra-revprop-change.c ... ------------------------------------------------------------------------ (which already shows that you forgot to show the svn:ignore property mods) > trunk/build/hudson/: > ------------------- > The hudson build system: > > jobs > README > More accurately, "configuration files for the hudson buildslaves we once tried to configure". They're not part of the build system.
