Building Subversion libraries with $ORIGIN option

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?
2. Is this worth trying? And if so, how would I go about doing it?
Are there some global settings I can make like CPPFLAGS? before
running a build that will cause this to be passed through to our
builds?

Any other thoughts?

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org