Re: mac os x framework linking target

On Jul 29, 2006, at 7:07 AM, Peter O'Gorman wrote: On Jul 29, 2006, at 11:54 AM, Daniel Rogers wrote: On Jul 28, 2006, at 4:10 PM, Peter O'Gorman wrote: Also, you seem to be looking at libtool-1.5.x which is not where any new feature would be implemented, you should probably check out

Re: mac os x framework linking target

Hehe, Ihad to reject my own post to this list as it was too large. We should probably consider it a bug that code to make a shared library from a 5 line .c file ends up as a 290kb gzipped tarball :-/ I had attached the following example to the message to daniel:

Re: mac os x framework linking target

On Jul 28, 2006, at 4:10 PM, Peter O'Gorman wrote: Also, you seem to be looking at libtool-1.5.x which is not where any new feature would be implemented, you should probably check out the libtool sources from cvs if you want to hack on them, however, I really don't think it a good idea.

Re: mac os x framework linking target

On Jul 29, 2006, at 5:48 AM, Daniel Rogers wrote: I'm interested in developing a "framework" building feature for libtool. Linking the shared library for a framework is exactly the same as linking a typical shared library. It's already quite close. The differences are described below, but

mac os x framework linking target

Hi, I'm interested in developing a "framework" building feature for libtool. Linking the shared library for a framework is exactly the same as linking a typical shared library. It's already quite close. The differences are described below, but they are summed up as, I need to be able to create a