|
Boost Testing : |
From: David Abrahams (dave_at_[hidden])
Date: 2007-09-04 09:52:02
on Mon Sep 03 2007, Vladimir Prus <ghost-AT-cs.msu.su> wrote:
>> http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html
>> error: Unable to find file or target named
>> error: '/boost/python//boost_python'
>
> As the message says "/boost/python//boost_python" neither file or
> *target*.
The message could be much better; '//' indicates that it's a target
name.
> Such target is only defined when you configure python in your
> user-config.jam
That's not accurate at all, unless someone has changed how this works
since 1.34.0 was released. In fact, it's backwards.
/boost/python//boost_python is declared when you import Boost.Python's
Jamfile from the libs/python/build directory. If you haven't
configured python in your user-config.jam, at that point, the jamfile
will attempt to automatically configure it.
I don't know who generates this message:
warning: Python location is not configured
warning: the Boost.Python library won't be built
but if that logic actually exists it sorta defeats the purpose of the
automatic configuration.
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com