Changes between Version 15 and Version 16 of PythonPort/Status


Ignore:
Timestamp:
Oct 28, 2007, 4:32:44 PM (18 years ago)
Author:
ghost
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PythonPort/Status

    v15 v16  
    11= Boost.Build Python port overall status =
    22
    3 == What works ==
     3== Status at a glance ==
    44
    5  * Interface between Python and Boost.Jam build engine is finished.
    6  * Project loading and target declaration works
    7  * Top-level code is ported, including getting build request, loading configuration files and
    8    projects and building/cleaning.
    9  * A simple project with a 'make' rule loads and builds fine
     5The majority of core modules are mostly done. The low-level interfaces with bjam are also finalized.
     6A simple project with a 'make' rule loads and builds fine. A simple performance test shows promising 7x
     7speedup.
     8
     9== Steps ==
     10
     11The port will proceed like this:
     12
     13 1. Initial port of core modules and the gcc toolset.
     14 2. Getting all unit tests and system tests to pass, with the gcc toolset.
     15 3. Cleanup the few terrible design issues (really few!)
     16 4. Port all other tools.
     17 5. Port all docs
     18 6. Release.
    1019
    1120== Status of porting code modules ==
     
    96105||doxygen-config.jam||11||pending||
    97106
    98 
    99 == Error reporting ==
    100 
    101 Review all raise statements. Make sure they don't include 'error' in messages. Convert
    102 them to use errors() as appropriate.
    103 
    104 Implement --stacktrace option for error reporting
    105 
    106 == Post port: code cleanup ==
     107== Design cleanups ==
    107108
    108109After all tests are passing with gcc, the following cleanups are desired:
     
    111112 * Introduce Property class, and no longer store properties as specially formatted strings
    112113 * Introduce Feature class, and don't use icky dict.
     114 * Cleanup error reporting -- review all raise statements. Make sure they don't include 'error' in messages. Convert them to use errors() as appropriate. Implement --stacktrace option for error reporting.
    113115
    114116== Post port: design cleanup ==
     
    117119 * Kill !ProjectAttributes and keep all information about project inside !ProjectTarget
    118120 
    119 
    120 
    121 
    122