Re: [Swarm-Support] OSX frameworks

[Bill Northcott]

> > However, it is not quite as simple as linking against the framework. 
In
> > order to have some chance of success, you also need to include the
> > framework's headers at compile time.  This is messy and requires 
changes
> > to the source code like:
> > #include <tcl.h> becomes #include <Tcl/tcl.h>.

> Or alternatively, specify -I /Library/Frameworks/Tcl.framework/Headers
> on the compile line. This avoids having to change the source code
> (except for the Makefile). I kind of assumed the previous poster had
> figured this out already. :)

Grumblings from OS X evangelist off stage:
If you are going to use -I you are throwing away the point of using 
frameworks.  You may as well stick the full library path in the link 
instruction.
The point of frameworks is to package libraries, headers and associated 
metadata into a distinct package at the file system level. If the 
framework options are used at both compile and link time, then all will 
work nicely even if a diffent version of the framework is installed at 
/Library/Frameworks ot $HOME/Library/Frameworks and therefore used.

All sorts of methods will work, but some ways of doing it are more 
portable and maintainable than others.

Billl Northcott