Re: purpose of the c wrapper

[Ralf Wildenhues]

Hello Vincent, Bob,

Bob already noted that the primary reason for any kind of wrapper, be
that a shell script or a compiled C program, for uninstalled programs
is so that uninstalled shared libraries are found when these programs
are executed.

Another reason is that, on some platforms, programs may need to be
relinked upon installation, and in that case, the wrapper provides the
necessary information to libtool to allow it to do the relinking at
'make install' time.  (This is for disabled or impossible fast-install
mode only.)

Whether a shell or a C wrapper is generated is currently a hardcoded
mess in the ltmain.m4sh script.  MinGW and Cygwin hosts will have a C
wrapper, so that the generated file will have an .exe extension, so that
it will satisfy the 'make' rule for the program.  (On most w32 systems,
a script without an .exe extension would match such a rule as well, but
that's not the case for example on GNU/Linux -> w32 cross compiles and
with some weird Cygwin mount options.)

Does there exist a simulator for wince?  Even if not now, can there
exist one at some point?  In that case, we should strive to not make
things harder for that setup.

But anyway, I don't see how the current git code generates C wrappers
for wince.  Can you post a small example Makefile.am that causes this,
and then post the failing 'libtool --mode=link' command, rerun it
manually with --debug added (you can stuff it in LIBTOOLFLAGS) and post
all output of that?

Thanks,
Ralf