Stuart Celarier wrote:
> Branko wrote:
>
>> If you had asked before, I could have told you that there are several
>> pseudo-projects there that let you build reasonable subsets of the
>> whole, and also that the dependencies between the projects are set up
>> correctly (at least for MSVC 6, but I expect for VS.NET, too) so that
>> setting the "svn" project as your default and building that will do
>> everything you need.
>>
>
> Okay, I didn't know to ask, so now I am asking. The INSTALL document in
> section II.E.4 says is to build __ALL_TESTS__. I couldn't find any
> mention or description of any of the other projects. What are all those
> other pseudo-projects for? How do I make use of all your hard work?
>
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.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 7 15:25:15 2006