[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: setting additional libtool runtime variables
From: |
mcmahill |
Subject: |
Re: setting additional libtool runtime variables |
Date: |
Mon, 15 Oct 2001 21:53:36 -0400 (EDT) |
On Mon, 15 Oct 2001, Gary V. Vaughan wrote:
> On Sun, Oct 14, 2001 at 10:03:38PM -0400, address@hidden wrote:
> >
> > Is there a way to tell libtool that it needs to set some additional
> > runtime variables in addition to LD_LIBRARY_PATH when trying to test run
> > an executible before its installed? I have some data files and the path
> > gets built into the binary, but can be overridden with an environment
> > variable.
>
> You could use a wrapper script that sets the environment up and then execs the
> real binary... CVS autoconf does this in the tests dir.
>
> Or you could set Automake's TESTS_ENVIRONMENT (sp?) variable in your
> Makefile.am.
This isn't part of the tests target, its more of a `let the user try it
before they install it'. Basically, I want the wrapper script setup by
libtool to contain an additional variable. It seems likes
TESTS_ENVIRONMENT is more for the make check target.
-Dan
- several automake questions, mcmahill, 2001/10/10
- Re: several automake questions, mcmahill, 2001/10/11
- Re: several automake questions, Alexandre Duret-Lutz, 2001/10/12
- Re: several automake questions, Raja R Harinath, 2001/10/12
- setting additional libtool runtime variables, mcmahill, 2001/10/14
- Re: setting additional libtool runtime variables, Gary V. Vaughan, 2001/10/15
- Re: setting additional libtool runtime variables,
mcmahill <=
- Re: setting additional libtool runtime variables, Raja R Harinath, 2001/10/16
- Re: setting additional libtool runtime variables, mcmahill, 2001/10/16
- Re: setting additional libtool runtime variables, Gary V. Vaughan, 2001/10/16
- target name not known until configure time, mcmahill, 2001/10/19