Hi,
I though that now that libtool-1.4 was released, I could finally have
my project to directly release a dll. Unfortunately, that is not the
case.
So I made a fake very simple library using autoconf, automake,
libltdl, libtool-1.4. Making it as clean as I could, reading the
autobook and libto
Sebastien Sable <[EMAIL PROTECTED]> writes:
> So I made a fake very simple library using autoconf, automake,
> libltdl, libtool-1.4. Making it as clean as I could, reading the
> autobook and libtool info pages. It works perfectly well under
> linux. It compiles without an
Guido Draheim <[EMAIL PROTECTED]> writes:
> why? using the latest in autotools does build a mingw-dll for me
> every week! Sure there are some problems but it works, just some
> extra arguments for libtool and extra lib references, that's it.
Well could you please specify those extra-argume
Hi,
sorry if this is not really specific to libtool but it I have this
little boring warning in a file of mine when using lt_dladdsearchdir :
gcc -DHAVE_CONFIG_H -I. -I. -I.. -DSYSCONFDIR=\"/usr/local/etc\"
-DPKGDATADIR=\"/usr/local/share/libbraille\" -DPKGLIBDIR=\"/usr/local/lib/libbraille\"
Tim Mooney <[EMAIL PROTECTED]> writes:
> It's not nothing, at least on architectures that aren't ILP32. Your program
> will work fine on Linux on Intel, but it will fail on 64 bit (LP64) OSes.
Sorry that was a really stupid mistake from me:
I was persuaded for some reason that the problem was
I have the following code that works (identbrl is not NULL and it
works ok when called) :
identbrl = lt_dlsym(library, "identbrl");
however if I add the following code :
identbrl = lt_dlsym(library, "identbrl");
strerror = lt_dlerror();
if (strerror)
{
Log(LOG_ERR, "%s", stre
When using mingw, libtool 1.4e (1.1198 2003/02/25 00:30:28)
with the --mode=install option will fail to install a .exe :
STRIPPROG='i586-mingw32msvc-strip' /bin/sh ../libtool --mode=install /bin/sh
/home/sable/tim/release_test/libbraille-0.9.11/libbraille-0.9.11/install-sh -c -s
test_libbraille
