hi all ...
i'm currently working on a build system based on build system for externals ... i found libtool on linux quite useful, but there are problems with libtool on osx ...
any hint by an osx guru, how an autoconf/autobuild/libtool package is supposed to look like on osx?
cheers ... tim
On Sun, Oct 17, 2004 at 01:12:50PM +0200, Tim Blechmann wrote:
hi all ...
i'm currently working on a build system based on build system for externals ... i found libtool on linux quite useful, but there are problems with libtool on osx ...
any hint by an osx guru, how an autoconf/autobuild/libtool package is supposed to look like on osx?
cheers ... tim
hi tim,
osx is quite complicated for linking. as far as i understand, there are 2 mechanisms (onelevel and twolevel namespaces).
in addition to that, there are 2 library formats: system library (dylib) and dynamic object. maybe this distinction is the same as above. the system lib is solved with libtool, and the other can be solved too, but i never understood how to do this actually.
there's a problem with 'budle loading' and chained dependencies too. an example for this is pdp/pidip on osx. in any case, if you want to use the standard 2-level module loading mechanism in libtool, you need to refer to the program that loads the plugin, being pd.
i currently solve it in pf using 1-level namespaces and dlopen from fink, but that's quite a messy workaround. to me it seems the sanest approach though. osx is really strange and not very friendly to the 'standard unix way' of doing things, as far as you can take solaris/linux to be the standard. you can turn this argument upside down of course.
cheers tom
Although I love libtool, I think that the building of externals is working quite well, especially on OSX and linux. Why should we take the burden of using libtool ?
Guenter
On Sun, 17 Oct 2004, Tom Schouten wrote:
On Sun, Oct 17, 2004 at 01:12:50PM +0200, Tim Blechmann wrote:
hi all ...
i'm currently working on a build system based on build system for externals ... i found libtool on linux quite useful, but there are problems with libtool on osx ...
any hint by an osx guru, how an autoconf/autobuild/libtool package is supposed to look like on osx?
cheers ... tim
hi tim,
osx is quite complicated for linking. as far as i understand, there are 2 mechanisms (onelevel and twolevel namespaces).
in addition to that, there are 2 library formats: system library (dylib) and dynamic object. maybe this distinction is the same as above. the system lib is solved with libtool, and the other can be solved too, but i never understood how to do this actually.
there's a problem with 'budle loading' and chained dependencies too. an example for this is pdp/pidip on osx. in any case, if you want to use the standard 2-level module loading mechanism in libtool, you need to refer to the program that loads the plugin, being pd.
i currently solve it in pf using 1-level namespaces and dlopen from fink, but that's quite a messy workaround. to me it seems the sanest approach though. osx is really strange and not very friendly to the 'standard unix way' of doing things, as far as you can take solaris/linux to be the standard. you can turn this argument upside down of course.
cheers tom
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list
Although I love libtool, I think that the building of externals is working quite well, especially on OSX and linux. Why should we take the burden of using libtool ?
well ... there is no proper build system for flext externals ... using libtool, it's very easy to build flext externals on linux ... so i'd prefer using libtool on other platforms, too ...
t
Hi Tim, as the Apple libtool for OSX is incompatible to GNU libtool i think it would be better to do the linking step without any of these tools. This is easy with flext too. Let's try it.
best greetings, Thomas
----- Original Message ----- From: "Tim Blechmann" TimBlechmann@gmx.net To: "guenter geiger" geiger@xdv.org Cc: "Tom Schouten" doelie@zzz.kotnet.org; pd-list@iem.kug.ac.at Sent: Monday, October 18, 2004 11:56 AM Subject: Re: [PD] libtool & osx
Although I love libtool, I think that the building of externals is working quite well, especially on OSX and linux. Why should we take the burden of using libtool ?
well ... there is no proper build system for flext externals ... using libtool, it's very easy to build flext externals on linux ... so i'd prefer using libtool on other platforms, too ...
t
-- mailto:TimBlechmann@gmx.de ICQ: 96771783 http://www.mokabar.tk
After one look at this planet any visitor from outer space would say "I want to see the manager." William S. Burroughs
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
On Mon, Oct 18, 2004 at 11:56:39AM +0200, Tim Blechmann wrote:
Although I love libtool, I think that the building of externals is working quite well, especially on OSX and linux. Why should we take the burden of using libtool ?
well ... there is no proper build system for flext externals ... using libtool, it's very easy to build flext externals on linux ... so i'd prefer using libtool on other platforms, too ...
i sort of have to agree with guenter here: libtool is not really going to reduce the complexity of the build process, because you will need platform-dependent flags anyway, as far as i understand. and unnecessary complexity is pure evil..
why not find out what these flags are for each platform, (one time programming :) and pass them to the linker manually? thomas' build system should have all the info.
the autotools are for portable programs across many unices. pd and especially libraries and externals do not really fit that shoe (always) i think..
to make sure i'm not talking bullshit, can you post the libtool flags you need to do this on osx?
-
guenter geiger -
Thomas Grill -
Tim Blechmann -
Tom Schouten