Re: Re: Building Langbinding

Alan Gutierrez <[email protected]>
Newsgroups gmane.comp.lib.boost.langbinding
Message-ID <[email protected]>
* David Abrahams <[email protected]> [2005-10-17 11:35]:
> Alan Gutierrez <[email protected]> writes:
> 
> >     I've got a learning curve on Boost::Build. Before I edit any
> >     files, I'd like to ask a few, hopefully simple questions.
> >
> >     The build directory appears to be ...
> >
> >     langbinding/boost/libs/python/build

> In what repository is this?

    http://cvs.sourceforge.net/viewcvs.py/boost/boost/libs/python/build/?only_with_tag=langbinding

> I can't find any such directory.

    Sorry, should have just sent a link. Got the root directory
    wrong anyway, that's what I named teh checkout directory.

> >     There is a Jamfile.v2 there that I'm going to start with, to
> >     build Langbinding on OS X. The relative paths indicate that a
> >     `touch project-root.jam` should be run in the build directory.

> You've lost me completely.

    I'm totally lost myself.

    bjam wants a project-root.jam , I tried putting one at different
    levels of the project structure, but the build still cannot find
    the headers.
    
    The CVS checkout for the langbinding branch included no context,
    only langbinding, the rest of Boost is not included in that
    branch, and when "pruned" CVS does not check it out. Header
    files for langbinding appear to go where they would belong if
    langbinding was within boost, under boost/langbinding, but the
    Jamfile.v2 will not find them.

    Anyway, I'm going to try to build in XCode against Python 2.2.

--
Alan Gutierrez - [email protected] - http://engrm.com/blogometer/


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.