[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: Tue, 16 Oct 2001 08:06:53 -0400 (EDT)

On Tue, 16 Oct 2001, Raja R Harinath wrote:

> address@hidden writes:
> > 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
> >>
> > 
> > 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 just happens that the 'autoconf' wrapper scripts are in the 'tests'
> directory.  You can use that approach in other places too.

When I set TESTS_ENVIRONMENT="FOO=bar" in, the only place it
seems to propagate to is in:

check-TESTS: $(TESTS)
        if $(TESTS_ENVIRONMENT) $$dir/$$tst; then \

ie, it never makes it into the libtool wrapper script.  Perhaps this has
changed in the developemnet branch of automake?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]