[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Patch] cwrapper invokes target directly
From: |
Ralf Wildenhues |
Subject: |
Re: [Patch] cwrapper invokes target directly |
Date: |
Tue, 27 May 2008 07:33:36 +0200 |
User-agent: |
Mutt/1.5.17+20080114 (2008-01-14) |
Hello Charles,
<http://thread.gmane.org/gmane.comp.gnu.libtool.patches/8429>:
* Charles Wilson wrote on Sat, Apr 26, 2008 at 10:22:39PM CEST:
>
> This patch also adds the following three command line options to the
> wrapper executable:
>
> --lt-env-set foo=bar
> --lt-env-prepend foo=bar
> --lt-env-append foo=bar
Why? I don't see any use case for this. In fact, I don't see how any
argument to the wrapper other than the dump-script one could ever be
useful: the user cannot (better: does not want to have to) know whether
the wrapper executable will be built for a certain uninstalled program
or not (think: it could be linked against an uninstalled library or
not). Further, if I want to modify the environment like
./prog --lt-env-set foo=bar
I can do
foo=bar ./prog
just as well, no?
In case you were hinting at supporting this
<http://thread.gmane.org/gmane.comp.gnu.libtool.bugs/5319/focus=5438>
for the cwrapper, well, that's not what you're doing, as Behdad's
feature request revolves around adding arguments to libtool --mode=link
which cause the uninstalled executable to have a modified environment.
*That* allows me to not have to differentiate between the call of an
uninstalled and an installed program at all.
What am I missing?
Thanks,
Ralf
- Re: [Patch] cwrapper invokes target directly,
Ralf Wildenhues <=