Stuart Celarier wrote:
>> Branko wrote:
>> The __ALL_TESTS__ project builds everything except the bindings -- all
>> the libraries, command-line tools and test programs.
>>
>> __ALL__ builds just the libraries and command-line tools (i.e., like
>> __ALL_TESTS__ but without the test programs).
>>
>> The __JAVAHL__, __SWIG_PERL__ and __SWIG_PYTHON__ projects build the
>> Java, Perl and Python bindings, respectively. Ruby bindings don't work
>> on Windows yet.
>>
>> There are of course separate projects for each command-line tool, each
>> test program and each library; the names should be self-evident.
>>
>
> Cool, thanks.
>
> Is there any reason this should *not* be in the INSTALL document?
>
Not really. Of course, we don't document all the various make targets
there, either; just the ones that you need to build and test Subversion.
Besides, just looking at the definition of those projects in the IDE
should be enough to figure out what they do.
No, I'm not against documentation, nut I don't believe INSTALL should be
the complete documentation for the build system; it's always been a
first-time user's introduction to building Subversion.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 8 02:00:24 2006