From: Mat Marcus (mat-lists_at_[hidden])
Date: 2005-06-29 01:47:58
-----BEGIN PGP SIGNED MESSAGE-----
- --On Tuesday, June 28, 2005 11:49 PM +0000 chiedo_a <chiedo_at_[hidden]>
> Hey everyone,
> I'm working with a group of people on a boost project and most members
> would rather not use the command line to build the boost libraries. My
> manager requested that I create a XCode project (using 2.1 on OS X
> 10.4.1) that builds a boost.framework file that will grant any project
> boost functionality when it is included. The framework must compile the
> headers and libraries using the .hpp and .cpp files. Does anyone have
> any suggestions on how to actually accomplish this?
> My current strategy is to basically read through the jamfiles and figure
> out which .cpp files are necessary for each library (most likely all the
> files in the ..../src directory). From there I should theoretically be
> able to just add these files to an xcode framework target and compile.
> Right? Are there any environment variables or compiler settings that are
> going to need to be set?
> Any help what so ever would be greatly appreciated.
Though I question the point of creating an XCode project to build boost as
a framework, here is how I would suggest that you proceed. Build the
libraries that interest you using "bjam -d2", together with any additional
build features/variants that you may require. The output from the above
command will give you the necessary list of files and compiler options. You
can then figure out how to build an XCode project that will produce the
same compiler options, using the required files. You can check your work by
comparing the XCode build results with the bjam -d2 output.
-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.0.1 (Build 2185)
-----END PGP SIGNATURE-----
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