On 2/1/2010 01:18, Roumen Petrov wrote:
JonY wrote:
On 1/31/2010 02:14, Roumen Petrov wrote:
I don't understand request as the usually final result is
.../libfool.la
.../libfool.dll.a
.../libfool.dll
.../libfool.a
Also note that makefiles the macros(variables) are libfoo_XXXX.
Did the requester expect if target is libfoo_XXXX make command to search
for libYYfoo_XXXX or may be requested will contact all developers as
will convince to use macros like @libpre...@foo_xxxx in makefiles and
LIBPREFIX is set by configure ?
Uhh ...
Hi,
If you looked at the concept patch, it changes how libtool names the
DLL by soname_spec, libname_spec stays the same. The makefiles do not
see the DLLs at all, only the .la files if libtool is in use. The .la
filenames stay the same.
That is the whole point of libtool, devs don't need to bother about
platform specific details and implementation of shared libs.
Uhh and the libtool install la files and process installed. So after
installation xx-bit will override yy-bit.
GCC already does the correct install for import libs for multilib
configuration with lib32,lib64.
For other packages that are not explicitly designed with multilib in
mind, use a different --prefix.
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
