[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: Dan Christian <dchristian_at_google.com>
Date: 2007-07-23 18:44:56 CEST

On 7/22/07, Mark Phippard <markphip@gmail.com> wrote:

> 1. Have you ever heard of this $ORIGIN token before or ever seen it used?

$ORIGIN is defined to be the directory the binary is in. You then have to
have a constant relative path from that binary to the libraries for it to
work. If anything changes that relative path (say copying a binary
somewhere), then it mysteriously breaks.

Libtool doesn't support $ORIGIN because there is no way to guarantee that
the relative path will stay constant. See this post (search down to
$ORIGIN):
http://72.14.253.104/search?q=cache:madI_vYhwWoJ:gcc.gnu.org/ml/gcc-patches/2001-02/msg00896.html+libtool+%24origin&hl=en&ct=clnk&cd=3&gl=us

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?
>

This could only be supportable if libtool does it. Libtool is doing a ton
of things to make libraries work on as many platforms as possible. Going
behind it's back won't work well or be easy to support.

What you really need is to be able to do the final libtool install step as
part of the install process. That would let you customize the install path
in a supportable way.

-Dan C
Received on Mon Jul 23 18:43:56 2007

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