Hi again! Sorry, i must correct myself. $EXEEXT *is* used *sometimes* and as far as my situation is concerned, completely in the wrong places...
I made the func_exec type of functions intelligent enough to recognize an exe with or without extension... For example tagdemo does this: func_require "tagdemo-make" "tests/tagdemo/tagdemo$EXEEXT" Which fails (of course) because the tests/tagdemo/tagdemo (without extension) is the wrapper around tests/tagdemo/.libs/tagdemo.exe .... I don't claim to have found a solution for this, but at least for now, and for me i got a workaround.... I think there is some work to be done here.... ;o) Cheers, Markus Duft Markus <> wrote: > Hi! > > I'm currently working on porting my wgcc patches from 1.5.22 to HEAD > (*pfff*). Now recently i changed the default output of wgcc to a.exe, > so i have an extension for my exe's, since otherwise they don't > really work that good in some cases ;o) > > However, no i realized, that the whole libtool testsuite does *not* > think about any possible extension, but simply calls the executable > with the basename only. > > In order to port my patches i need the testsuite to recognize exe's... > What should i do? > > Cheers, Markus > > > _______________________________________________ > http://lists.gnu.org/mailman/listinfo/libtool _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
