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
a) add the libraries to your project instead of just setting the
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?
> - 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: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Sep 11 13:13:15 2007