Changes between Version 3 and Version 4 of PythonPort

Timestamp:

Oct 10, 2007, 12:51:24 PM (18 years ago)

Author:

ghost

Comment:

--

PythonPort

@@ -1 @@
-= Python port information =
+= Boost.Build V2 python port =
 
-There's highly experimental Python port of Boost.Build V2. It's currently not intended for users at all, and unless you're willing to develop it, we suggest you don't even look at it.
+This page describes porting of Boost.Build to Python. This page is only of interest of developers willing to help
+with the port.
 
-If you're willing to work on that port, follow these steps:
+== Why? ==
 
- * Get CVS version of Boost.Build V2
- * Run the following command from the source root:
-{{{
-cvs up -r BOOST_BUILD_PYTHON python
-cvs up -r BOOST_BUILD_PYTHON pybb.jam
-}}}
+Boost.Build V2 is mostly implemented in the interpreted language of the underlying build tool, and it has
+a number of problems:
 
- * Build {{{bjam}}} with Python support:
-{{{
-./build.sh --with-python=/usr
-}}}
- * Set the {{{BOOST_BUILD_PATH}}} to the directory where Boost.Build is located.
+  * No user knows that language, making it hard to extend Boost.Build or become new developer.
+  * The language is strange at times, and not very nicely documented.
+  * There's no standard libraries, so every new functionality should be implemented from scratch
+  * The only data structure in the language is list of strings. This makes many tests cumbersome, and leads to excessive memory consumption and poor performance on some workloads.
 
- * Go to {{{python/tests/bjam/make}}} and run:
-{{{
-bjam --build-system=pybb
-}}}
-The expected effect is that the {{{a.cpp}}} file is copied to {{{a}}} file.
+== How? ==
+
+The Python port is supposed to be 1:1 translation, with only mechanical changes. The language used to describe targets will
+not change, and all tests won't be altered. The port will be declared complete when all files are ported, and all tests pass
+using ported version. 
+
+== Hacking and trying ==
+
+
+