shared libraries in windows port (was: r13637 - gnucash/trunk - Add more linker flags)

Christian Stimming stimming at tuhh.de
Thu Mar 16 04:29:11 EST 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Mike,

Mike Alexander schrieb:
> I haven't been following the Windows port much (I get enough grief with
> Windows development in my day job), but it sounds like the idea is to
> treat everything like a shared library on Windows and not have any
> loadable modules.  Is that more or less correct?  

No, that's not what we (more precisely: I) try do to. We "just" create
the libraries through libtool in the very same way as the Unix/Mac
versions, except that libtool requires the "-no-undefined" flag on
windows for everything in order to build shared libraries. The resulting
files will always be DLLs on windows. I can't tell whether there is
still a difference between a loadable module and a shared library.  They
might be different, but maybe not.

The problem rather is that the windows libtool due to the
"-no-undefined" flag requires *all* library requirements to be specified
explicitly and fulfilled at linking time. This is different from what we
used to have on Unix/Mac, where the majority of library requirements
were either inferred at link time from a small number of explicitly
specified libraries and/or they were unfulfilled at link time but were
fulfilled/resolved only at runtime. Because of either one of this two
reasons we were not required to list all actual library requirements at
link time, and somehow it worked out fine at runtime.

> If this is correct then I don't think it's necessary.  You should be
> able to keep the idea of loadable modules on Windows.  We do that all
> the time in my day job.  

Yes, that's what my basic assumption was, too. Thank you for confirming
again that this will actually work out as expected.

Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBRBkv52XAi+BfhivFAQLZqQP/YvgGFoZzhBANolKYvmp2DCxc3JeRRLS1
AbrSoFowwJamkKn8bPkR8k8LW1aMS3waefWJOTKScyJupEgmDNYP/C0hMnX1yHAh
5DiFsdwWA/umFDsR8zR23U33I4BJ/+xdqqDP5Xhqi9kUhtpKCzvZN4UFijjxi+pM
Z4Xu8naZnas=
=iu1i
-----END PGP SIGNATURE-----


More information about the gnucash-devel mailing list