Mac OS X -module (was Re: Confusion about use of G2)

Peter O'Gorman peter at pogma.com
Sun Oct 2 19:27:50 EDT 2005


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

Neil Williams wrote:
| There are also architectural changes to the makefiles for libraries that use
| -module for G2 to work on Mac OSX. Those warnings that we all see about
| linking executables against ... library not beng portable - those warnings
| bite on OSX and those were not a problem with the 1.8 tree (I think due to
| the version of gcc available for 1.8). They will, however, halt the build of
| any G2 package if not fixed.
|

If you look at configure.in, you'll see a god awful hack to change the value
of archive_cmds on darwin after libtool is generated. I put the hack in
there in preference to changing lots and lots of Makefile.am's. If you want
to change the Makefiles so that the loadable module only contains the file
which has the gnc_module_init functions and it links to all shared library's
needed so that there are no undefined symbols anywhere (I believe this would
also greatly improve the chances of a working windows build), that will
solve the problem.

I suggest the short term hack of adding to the ugly sed hack in configure to
set libtool's "module_cmds" var to nothing. eg. -e
's,^module_cmds=.*,module_cmds=,g' or something, this will make the build
better on OS X. I don't understand how you aremanaging to build on OS X at
the moment though.

Peter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Darwin)

iQCVAwUBQ0Bs9biDAg3OZTLPAQIfnQP9FF8ZehAimSI/SUER3oG/kRj6FpQXpUrC
tb8UZABBE5ZHJoY1pQkAh/LFXwYNuUQXQRcs28x7Qmka0pKH6q0lsetMoJUAFMcb
aUPNsZoHbE3IBgwXJ+tETo4+TXmAIjXx8lpsFvxQoaYAZZzWct3XbxduUwhHx7XC
771iY3XB2Dg=
=sUn5
-----END PGP SIGNATURE-----


More information about the gnucash-devel mailing list