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

Re: Building Subversion libraries with $ORIGIN option

From: Blair Zajac <blair_at_orcaware.com>
Date: 2007-07-23 04:41:37 CEST

On Jul 22, 2007, at 6:53 AM, Mark Phippard wrote:

> A Subclipse colleague sent me this link:
>
> http://www.itee.uq.edu.au/~daniel/using_origin/
>
> A problem we have been trying to solve forever with Subclipse is a way
> that we could distribute JavaHL to Linux and Mac users as part of
> Subclipse. Eclipse gives us a way to physically ship the bits, and it
> even does some magic so that when we load the library from Java it is
> found. However, that is where the magic ends. When the library is
> loaded, it loads all of its dependencies using the normal library
> loading rules of the OS.
>
> If we ship JavaHL and the Subversion libraries with Subclipse, they
> are all going to be located in some random folder in the filesystem.
> We do not have any way to install these into some system location like
> /usr/lib (nor would we likely want to).
>
> The above link appears to describe a way to build a library so that at
> runtime it will try to load its dependencies from the same location
> where it is located. In theory, this sounds like what we want with
> Subclipse. We can successfully find and ask the JavaHL library to
> load. If we could build everything so that it then looked in that
> same location to load everything else, it could work.
>
> So here are my questions for you build gurus:
>
> 1. Have you ever heard of this $ORIGIN token before or ever seen it
> used?

No, I've never heard of it.

Is this Linux specific? Does it support Solaris, or other non-Linux
Unix OSes? Do you care to support them?

Blair

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 23 04:40:40 2007

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

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