I don't know how useful this will be to people but I wrote an Ant build
file to build subversion & javahl and then run the javahl unit tests. It
can also create a distribution.
This is not something I currently maintain for public consumption. It's
not pretty and I had to do a few manual tweaks to some files. Also, I'm
focused on SVN client development, so I don't worry about the server
side of things (httpd, etc). Nevertheless I find it makes it easy for me
to repeatably build svn/javahl on Windows.
It's attached - YMMV.
Conor
Patrick Mayweg wrote:
> Hi Mark,
>
> Mark Phippard wrote:
>
>> Daniel Rall <dlr@finemaltcoding.com> wrote on 04/14/2005 11:05:34 AM:
>>
>>
>>
>>> Folks, is there a canonical location for Windows development where
>>> information like this should be documented?
>>>
>>
>>
>> I would love to see this document greatly expanded:
>>
>> http://svn.collab.net/repos/svn/trunk/subversion/bindings/java/javahl/README
>>
>>
>>
> Right now, I do not have time for that, I am really happy for any
> patches. I am also not good in writing these things in a end-user
> friendly way.
>
>> It seems to me that there is a huge number of *nix users of Subclipse
>> that absolutely cannot figure out how to build JavaHL from source. On
>> Windows, if you can get the main Subversion build to work, then JavaHL
>> is pretty easy. There are just a couple of steps to take care of,
>> that could be described better.
>>
>>
> For *nix, the way to build is not much more difficult.
> On the configure command, you have to add "--enable-javahl". If that
> does not find your jdk add "--with-jdk=(Path to jdk)". If you want to
> run the test add "--with-junit="(Path to junit jar)".
> Run
> make
> make javahl
> make install
> make install-javahl
> make check-javahl
> There is a patch, that you do not need to install javahl to be able to
> run the tests.
>
>> I really want to build an entire JavaHL "site" within the Subclipse
>> web site. I haven't done so thus far because I do not want to bite
>> off more than I can chew, and I just do not have the depth of
>> experience on *nix to cover the issues.
>>
>> A detailed build from source explanation would be a great start, but
>> the next thing would be info that is specific to distributions, such
>> as how can I tweak the Debian package to build and install JavaHL, or
>> the RedHat RPM's etc... Then there are also other issues such as on
>> Debian, the JavaHL library will not be found by default, apparently
>> because something called LD_LIBRARY_PATH is not set.
>>
>>
> There 2 different thinks for loading native code.
> The first is to tell java where to look for native code. That is the
> system property "java.library.path". The default for that is normaly the
> path where to look for dll's/shared libraries/shared objects/whatever.
> On Windows its PATH and on Linux it is LD_LIBRARY_PATH. On other *nix it
> is different. Beginning with 1.2 you can also set the system property
> "subversion.native.library" to the fully quallified name of the
> dll/shared library/shared object/whatever.
> The second is where java the depend like apr is located. That is
> normally the above path, but on Linux and other "*nix", you can link a
> path to depend in the native code.
>
>> If some good docs could just be maintained in the Subversion
>> repository, I would be happy to take ownership of making an end-user
>> friendly web site with similar info.
>>
>>
> I will be happy to take care of maintaining it.
>
>> Mark
>>
>>
>>
>>
> Patrick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 15 10:44:57 2005