Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo


#11 Compiling - Boost problems under OS X

Jonathan Merritt

For cgkit-2.0.0alpha7 under OS X, I installed boost using macports (www.macports.org) using the command line: sudo port install boost +python. (+python is required in order to install the python extensions to boost)

Then, in order to get cgkit's setup.py to recognize the installed Boost, I had to add the following to config.cfg:
INC_DIRS += ['/opt/local/include/boost-1_33_1']
LIB_DIRS += ['/opt/local/lib']
(Paths appropriate to default Macports, but milage will vary with Fink, etc.)

It might be useful to add notes about this to the OS X build information, since the scons build scripts report that Boost is successfully installed for supportlib, but setup.py then fails.


    • status: open --> pending
  • Matthias Baas
    Matthias Baas

    Logged In: YES
    Originator: NO

    Actually, I don't remember why I put /opt/local/include into the supportlib SConstruct file in the first place. This must have been a request by a user as this path doesn't exist on any of the systems that I was using (until now).
    But I agree that the Scons build and the distutils build should use the same default paths. I will change that.

    However, I don't know what to put there by default. Meanwhile I don't encourage using the MacPorts version of Boost.Python anymore as I even tend to consider it to be broken. It does not link against the MacPorts version of Python but against the Apple (framework) version of Python which might lead to a version conflict if the Python versions don't match. Besides that it cannot be used for Intel Mac users who want to compile the Maya/Python stuff because the MacPorts builds don't produce universal binaries whereas Maya is currently only available as a PowerPC version, so the plugin has to be compiled as a PowerPC binary as well. That's why I was compiling Boost.Python as a universal binary myself and put it into /usr/local.

    I think I will add both paths, /opt/local and /usr/local, to the default paths and provide a way for users to *remove* paths whenever this is necessary.

    - Matthias -

  • Matthias Baas
    Matthias Baas

    • milestone: 195388 --> Missing_feature
    • status: pending --> open