From: Joel Beaudoin (joeldoin_at_[hidden])
Date: 2007-10-26 19:24:03
Sorry. Both would be nice, but I'm specifically writing about a
framework for C++ Boost.
Once you have the tree, as documented by Apple, that's your framework
right there. OSX Boost users can then just add '-framework Boost' to
gcc for building projects that include Boost and it will find what it
needs. This script will give you an idea of what I'm doing outside of
the Boost build system to get a framework:
For completeness an Info.plist file should be written into the
Resources directory of the framework tree, but I'm not doing this in
the script yet.
I apologize if this should have been sent to the developers list
On Sep 12, 2007, at 2:32 PM, Vladimir Prus wrote:
> On Friday 26 October 2007 22:50:57 you wrote:
>> I would imagine the interface would be the same with the addition of
>> something like --framework-osx as an option for mac builds. I don't
>> think the OSX framework structure supports variants (debug/release,
>> multithreaded, etc.) very well; only different versions of the same
>> variant. I just build a release, singlethreaded framework for my
> Err. To clarify -- you are talking about building C++ Boost, or
> support for OSX frameworks in Boost.Build?
> Also, assuming I have directory tree just like the framework expects,
> how can I convert that directory tree into framework?
> - Volodya
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk