On 2 November 2010 13:26, Charles Wilson cyg...@cwilson.fastmail.fm wrote:
On 11/2/2010 2:14 AM, Ralf Wildenhues wrote:
...
the problem is there are TWO different libuuid's. There's the one that
is part of the win32 api, and simply contains a number of static objects
that represent UUIDs of
Hello,
I have came across a libtool issue that complicates my life quite much.
The essence of the problem is that libtool refuses to make a DLL if it
is supposed to link a static library into the DLL. I have learned that
this is a good assumption since the majority static libs don't contain
PIC
I'm trying to understand the libtool current:revision:age versioning
scheme. I think I understand how it works, but I noticed that filename of
the shared library seems to get different numbers
(current-age.age.revision). Is that expected?
The filename generation is dependent on the OS. It
On Tue, 2010-01-26 at 23:26 +0800, JonY wrote:
...
I suggest the following naming scheme.
mingw.org:libname-major.dll (unchanged)
Cygwin: cygname-major.dll (unchanged)
mingw-w64(64):lib64name-major.dll
mingw-w64(32):lib32name-major.dll
libtool should
On Wed, 2010-01-27 at 22:19 +0100, Peter Rosin wrote:
Den 2010-01-27 20:54 skrev Matěj Týč:
On Tue, 2010-01-26 at 23:26 +0800, JonY wrote:
...
I suggest the following naming scheme.
mingw.org: libname-major.dll (unchanged)
Cygwin:cygname-major.dll (unchanged)
mingw-w64
Hello,
if I link to a library that uses pthreads (for example OpenEXR suggests
the -pthreads LDFLAG -- taken from OpenEXR.pc pkg-config file), I can
see that unlike library dependencies this dependency propagates further
like some disease. Even if my product is a library or a module, not only
that
Hello,
this is ltdl-related, especially related to the case when you try to
open an invalid module without knowing that it actually is invalid.
The story is that if you try to lt_dlopen a module that can't be
dlopened (for example when it has unsatisfied dependencies), the
lt_dlopen function will
Hello,
if you want to lt_dlsym functions from your modules, how do you do that?
If you write Windows libraries, you have to dllexport stuff, however GCC
4 supports the same feature, there you have to use visibility(default)
stuff.
There is something about this in the libtool manual (section 11.2):
It seems that the current build directory is implicitly passed as an
-L. flag to the libtool-supervised linker
No. Well, first off, until this message of yours, I didn't know that
/home/bubla/projects/devil_modular/lib/ was the current build directory.
Hmm. This line in
Maybe one question towards libtool maintainers is left:
Is that detection of lib/libjpeg.la a desired behavior? I just pass
-ljpeg as an LDFLAGG, not as a LIBADD library...
Yes, it is. It is also intentional that .la files are installed
(of course for non-convenience archives only), and
Hello,
I use autotools libtool to make a library. That library consists of the
main shared library file and a set of dynamically loadable modules.
Those modules depend on external shared libraries.
I have written configure.ac and Makefile.am that are quite complex and
some things are generated
/bin/sh ../libtool --tag=CC --mode=link gcc -DNOINLINE -Wextra -g -O0
-module -lpng12 -o png.la -rpath /usr/local/lib/IL png_la-il_png.lo
-lm -lz
results in:
libtool: link: gcc -shared .libs/png_la-il_png.o -lpng12 -lm -lz
-Wl,-soname -Wl,png.so.0 -o .libs/png.so.0.0.0
That
In the directory /home/bubla/projects/devil_modular/lib/ you have a
libjpeg.la file. This is not the jpeg module that you are creating, it
is a different library. libtool finds this when you pass -ljpeg (not
sure why, as there is no -L flag for that directory). This libjpeg.la is
a libtool
Hello all,
I am using libltdl in my project and I experience some unexpected things.
First of all, if I have some undefined references in my module, the
module can't be loaded using lt_dlopen neither using its ext variant.
The reason for that is stated as could not find the file, but this
is not
Yes, it may be a good idea if somebody wrote this.
It should probably depend on LT_OUTPUT.
OTOH, the havelib module from gnulib already provides quite a bit of
functionality in this area.
OK, but what should I tell to the library users? Using gnulib is quite
troublesome since
it does not
Thank you for your reply, Ralf
This is not possible, in general. It has nothing much to do with
libtool either, because typically it's just the system semantics that
allow for only one unversioned soname symlink.
OK, but an easy check whether I can safely link with the lib would be nice, too.
Hello,
I have a library that has its .la file in the right place.
The question is: What should I do in the autotools setup so that libtool
takes over the compilation, discovers the .la file and passes additional
options to the linker so that the linking doesn't fail? Having
AC_PROG_LIBTOOL in the
Hello,
libtool has a nice way how to version libraries.
However, how do I tell to the linker that my app has to link with the
library that supports interface x?
This seems as a very trivial question, but I haven't found the answer in
the manual, is that possible?
Regards,
Matej
Hi all,
I am seeking a howto regarding making DLLs for Windows. I have found
some information about DLLs here
http://www.freesoftwaremagazine.com/books/agaal/building_shared_libraries_once_using_autotools
some in the goat book
Greetings to all of you,
I would like to use libtool with a multiplatform library that has some
complicated structure (ASM routines, some 'main' function hijacking
etc.) I think that libtool may be the right tool for managing the build
and the linking afterwards.
So imagine this situation: You
20 matches
Mail list logo
