[Boost-build] 2nd try: Python/Cygwin support in v2

From: David Abrahams (dave_at_[hidden])
Date: 2006-12-23 13:07:40

David Abrahams <dave_at_[hidden]> writes:

> 1. cygwin-condition: there's a comment now, but it's still quite
>    unclear.  How should this argument be used?  We need an example.
>
>    I'm beginning to think it should look something like:
>
>          <toolset>gcc
>
>    The comment says, "should be a set of properties which are present
>    when we're building with cygwin gcc," but (if my theory above is
>    correct) that fails to indicate the primary distinguishing feature
>    of the argument, which is that it must identify the cygwin-gcc
>    toolset.
>
> 2. Also the comment says: "This argument is not used yet," but it
>    clearly /is/ used.  Code branches are followed based on its
>    value.
>
> 3. The logic in this file that is used when the cygwin branch is
>    followed seems to have been copy/pasted from the v1 python support,
>    with all kinds of ends left dangling.  For example, what do all the
>    CYGWIN_PYTHON_DEBUG_* variable settings do?  Nothing AFAICT.

Hello?

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