Boost logo

Boost-Build :

From: David Abrahams (dave_at_[hidden])
Date: 2006-07-22 08:31:20


Vladimir Prus <ghost_at_[hidden]> writes:

> On Saturday 22 July 2006 16:05, David Abrahams wrote:
>> Vladimir Prus <ghost_at_[hidden]> writes:
>> > I've just checked in the attached. Let me know if something looks wrong.
>>
>> a. I don't see python_for_extensions defined anywhere
>
> It's defined in python.jam, and was defined for quite some time, just not
> used.
>
>> b. At the very least, the comments are wrong for the Windows platform,
>> where extending applications _do_ link directly to the
>> libpython.lib import library.
>
> And which comment is wrong? This one:
>
> + # We don't link to Python library itself. If
> + # Boost.Python is used for extension, all Python
> + # symbols are available in Python interpreter.
> + # If Boost.Python is used for extending, client
> + # is required to link to /python//python itself.
> + <use>/python//python_for_extensions
>
> ?

Yes.

> How about this rewording:
>
> # On Linux, we don't link to Python library itself. If
> # Boost.Python is used for extension, all Python
> # symbols are available in Python interpreter.
> # If Boost.Python is used for extending, client
> # is required to link to /python//python itself.
> # On Windows, all code using Python has to link
> # to python import library. The 'python_for_extension'
> # is the target that's setup to provide either just
> # include paths, or import library.
> <library>/python//python_for_extensions
>
> ?

A bit wordy, but better than before, thanks. It's accurate now.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com

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