[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Compiling minimal_client on MacOS X

From: B. Blodau <b_blodau_at_hamburg.de>
Date: 2007-09-11 16:56:33 CEST

Hi Jeremy,
thanks a lot for your help.

I already tried to use the static libraries instead of the dynamic
ones, but they seem to be incomplete. At least with my installation
of the 1.4.4 version, there are no libapr, libaprutil static libraries.
Building them via the source code, results in compiler errors for at
least xmltok_impl.c, which is part of the apr-utils. I'm wondering
which compiler settings may be necessary to compile it.
In the neon project I'm also getting compiler errors, that - e.g. -
gnutls.h can't be found. Do I have to install anything else?

If in your case, using the souce is straight forward, would may I do
wrong? I just set up an XCode project for a tool and added the
include paths and the code and it should work fine.
And yes, I ran the configure tools before trying to compile.


Am 11.09.2007 um 13:15 schrieb Jeremy Pereira:

> On 10 Sep 2007, at 20:16, B. Blodau wrote:
>> Hi Jermey, hi everybody else!
>> However, after the first time of joy about the successful run of
>> the app, I found out that the linker is not adding the code to my
>> app, but only referencing it. When I run the app on a system
>> without SVN installed, it can't load the libraries.
>> What I need, is a stand-alone app which can run even if SVN is not
>> explicitely installed on the users machine.
> I think you have two choices.
> Either build or obtain static versions of the Subversion libraries
> and other dependencies and link with them instead of the dynamic
> libraries. I'm not quite sure how you would tell XCode to use the
> static libraries instead of the dynamic ones. Two possible
> approaches are
> a) add the libraries to your project instead of just setting the
> loader flags.
> b) put the static libraries in a separate directory and point the
> library search path to that directory
> NB static libraries have a name of the form libxxxx.a instead of
> libxxxx.dylib so if you have libsvn_client-1.a somewhere on your
> system, that is the static library.
> The other option, if you are building a Mac OS X application
> bundle, is to stick with the dynamic libraries but include them in
> your bundle.
>> So my questions are:
>> - is generally possible to add the libraries to the app?
> See above
>> - am I allowed to to so, or may this be violation of SVN rights?
> Yes it may. However, it is not that onerous to comply with their
> licence. See the file called "COPYING" in the top level of the
> source distribution and the licences of the dependencies e.g. apr
> and neon to find out what your obligations are.
>> - does anybody has experience with building the SVN source code
>> (the .c stuff) on the Mac? Just for the case, that there is no
>> other way to build a stand-alone application.
> Yes, I always build Subversion from source except on Windows. It's
> pretty straight forward, except you don't get fat binaries.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 11 16:53:36 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.