[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fink-devel
Subject:    Re: [Fink-devel] .so vs .dylib
From:       "Peter O'Gorman" <peter () pogma ! com>
Date:       2006-05-31 23:20:25
Message-ID: 1149117625.16685.6.camel () tww ! local
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Wed, 2006-05-31 at 09:25 -0400, David Reiser wrote:
> This isn't necessarily a fink question, but it might get to be...
> 
> A change was made in gnucash 1.9.7 where the program looks to load  
> a .so module, but the compiler/linker only created .dylib files. The  
> object in question is a Mach bundle. Creating a symlink  x.so ->  
> x.dylib does allow everything to work, but it seems like an ugly fix.  
> Where should I be looking to find documentation on the proper  
> approach to either create a .so file in the first place, or let the  
> program look for .dylib files in the case of a Darwin system?
> 
> Their one mac developer has moved on to other projects, and I'm  
> trying to keep the mac friendly ball rolling with limited knowledge  
> on my part.

Neil moved on?

Gnucash has a whole bunch of libraries that are also loadable modules
and is one of the reasons that dlcompat got written all those years ago.
Gnucash-1.8 and 1.9 may differ in this regard though, I do not know.

1.8 always uses libltdl or guile to load modules, and guile always uses
it's own libltdl, libltdl has a hard-coded-at-compile-time idea of what
the loadable module extension is, and depending on the libtool version,
that will either be .so or .dylib on darwin. This should not matter if
the .la files are kept around though, as the .la file has the dlopenable
name in it.

gnucash-1.9 probably still uses libltdl to open modules, doesn't it?

Peter

["signature.asc" (application/pgp-signature)]



_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel


[prev in list] [next in list] [prev in thread] [next in thread]