Thanks to everyone, particularly rafl, for getting shared libraries
in. I hope that it hasn't been too painful, and that we get support
for most platforms.
Here's a patch which provides initial support for Darwin. I've only
just got a Mac, so am learning as I go along (e.g.
http://fink.sourceforge.net/doc/porting/porting.en.html)
I've basically added a way to suppress the -rpath flag when building
shared libraries, and done a -install_name to do the rpath
functionality (but on the library, not the executable that links with
it; hence the inconsistency that I'm going to mention now).
For simplicity, I've gone and broken my own naming convention for
config variables. In the next day or so I'll probably submit a patch
to change some of the names,
e.g. libparrot_soname -> ld_libparrot_share_flags
rpath_blib -> link_libparrot_share_executable
[or /something/ like that]
Hence they describe where they are used, not what they contain.
Cheers,
Nick
On Jan 5, 2006, at 3:45, Nick Glencross wrote:
> Thanks to everyone, particularly rafl, for getting shared libraries
> in. I hope that it hasn't been too painful, and that we get support
> for most platforms.
Fighting with Win32 still ...
> Here's a patch which provides initial support for Darwin.
Not directly applied - shared config items already changed, but I've
extracted (hopefully) relevant settings. Anyway, it works now, but ...
> e.g. libparrot_soname -> ld_libparrot_share_flags
> rpath_blib -> link_libparrot_share_executable
... especially 'rpath_blib' is really a hack now, it's just "-L".
Thanks,
leo