Hi,
Guile uses libtldl to do its dynamic linking and we decided to ship
our own copy of it (suitably renamed) since we found that libltdl
contained some showstopper bugs and we wanted be able to fix them
quickly without having to wait for a libtool releases and also to be
sure that people use the
Earnie Boyd wrote:
Is it still true that global variables exported from a dll must have a
dllimport directive for applications? AC_LIBTOOL_WIN32_DLL would
perhaps indicate a package has addressed this issue (by whatever
means) and is therefore dll safe.
While this is required by MSVC, to my
Oops. Looks like the uuencoded version of egor's stuff got scrambled.
I've MIME-atteched them here.
--Chuck
egor-patches-example.tar.bz2
Description: Binary data
long_long_example.tar.bz2
Description: Binary data
This is good info, however, the more pressing matter is that I don't
see any evidence that AC_LIBTOOL_WIN32_DLL currently supports a
flag which determines if DLLs will built.
There is the variable lt_cv_cc_dll_switch but this is not used at all
by Cygwin anymore, and MinGW only uses it as a means
IMO, libtool should simply try and build the dll. If dll's need to be
disabled, let the author do that via configure.in.
What means is provided to absolutely disable building DLLs (without
disabling building shared libraries in general) via configure.in?
Bob
