Changes between Version 4 and Version 5 of PythonPort


Ignore:
Timestamp:
Oct 10, 2007, 1:39:31 PM (18 years ago)
Author:
ghost
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PythonPort

    v4 v5  
    1616== How? ==
    1717
    18 The Python port is supposed to be 1:1 translation, with only mechanical changes. The language used to describe targets will
    19 not change, and all tests won't be altered. The port will be declared complete when all files are ported, and all tests pass
    20 using ported version.
     18The Python port is mostly 1:1 translation, with only mechanical changes. The language used to describe targets will
     19not change, and the Boost.Build testsuite won't be altered. The port will be declared complete when all files are ported, and all tests pass using ported version.
    2120
    2221== Hacking and trying ==
    2322
     23The source for the Python port is in Boost SVN: [http://svn.boost.org/svn/boost/branches/build/python_port]. There are some changes required in the Boost.Jam build engine, those changes are checked in to trunk: [http://svn.boost.org/svn/boost/trunk/tools/jam]. If
     24you're a Boost developer, for read-write checkout, use the "https" scheme when checking out the source.
    2425
     26See PythonPort/Quickstart for getting up and running.
     27The PythonPort/Design page documents the design decision specific to the python port, as well as important parts of pre-existing design.
     28The PythonPort/Process documents how the porting is performed.
    2529