[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Handle -o w/ and w/o $EXEEXT during manifest embedding
From: |
Ralf Wildenhues |
Subject: |
Re: Handle -o w/ and w/o $EXEEXT during manifest embedding |
Date: |
Sun, 31 Aug 2008 07:29:26 +0200 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
Hi Peter,
thank you for starting a new thread on this. The other, monster thread,
scares me a bit too much for wanting to dig through it.
* Peter Rosin wrote on Sat, Aug 30, 2008 at 10:26:45PM CEST:
>
> During my exercise with libsndfile I found a problem with
> the manifest embedding code. $output may or may not contain
> the trailing $EXEEXT, so the code in $postlink_cmds has
> to handle both cases (or some c14n has to be added to ltmain).
Is this really a problem with the libtool variable exeext not being set
correctly, or with the libtool script being passed '-o prog' vs. '-o
prog.exe'?
If it's a problem with exeext not being set correctly, then shouldn't we
fix that? Markus Duft posted a patch for that on this list before,
which I've never found the time to evaluate.
Also, this needs testsuite exposure if not already done.
Thanks,
Ralf
> 2008-08-30 Peter Rosin <address@hidden>
>
> * libltdl/m4/libtool.m4 (_LT_LINKER_SHLIBS)
> [ cygwin, mingw, cegcc ] <cl*>: @OUTPUT@ may or may not
> include a trailing $EXEEXT. If mt fails, make sure libtool
> exits with an error.
> (_LT_LANG_CXX_CONFIG): Likewise.