On Thu, 17 Apr 2014, Evgeny Grin wrote:
Hi!
Libtool always build static lib if dynamic lib can't be created.
This behavior is inconsistent with other build tools. For example if GCC can't
compile something, it fail with error.
If I need a shared lib, this doesn't mean that static lib will
On Thu, 17 Apr 2014, Evgeny Grin wrote:
Hi,
It's strange for me that last line in following qoute from ltmain.in is
commented out:
---
# It is impossible to link a dll without this setting, and
# we shouldn't force the makefile maintainer to figure out
# what system we are
On Thu, 17 Apr 2014, Evgeny Grin wrote:
Hi!
Win32 libs is forced to be static if any dened lib is not shared.
If it's done to prevent symbols conflicts on several shared libs with same static lib.
But if DEF file is used or dllexport function attribute is used, ld will not export
functions
18.04.2014, 19:17, Bob Friesenhahn bfrie...@simple.dallas.tx.us:
Why does it create more headache when porting to Win32? Using this
option indicates that the project has been constructed in a way which
will work on systems which do not allow undefined symbols. Many
projects (particularly
18.04.2014, 19:25, Bob Friesenhahn bfrie...@simple.dallas.tx.us:
For Win32 builds on my Windows system, I see that it is normal for
DLLs to be named according to the major interface number. For
example, zlib (not created using libtool) is named zlib1.dll and
libltdl (created using libtool)
On 4/19/2014 03:31, Evgeny Grin wrote:
18.04.2014, 19:25, Bob Friesenhahn bfrie...@simple.dallas.tx.us:
For Win32 builds on my Windows system, I see that it is normal for
DLLs to be named according to the major interface number. For
example, zlib (not created using libtool) is named
19.04.2014, 04:45, JonY 10wa...@gmail.com:
On 4/19/2014 03:31, Evgeny Grin wrote:
For XBMC we have 41 depend precompiled lib, 4 of them depend on zlib dll,
all of 4 depend on zlib1.dll, but each one on specific zlib version. And
with some zlib versions some of depend dlls crash.
But
