Permalink
Browse files

Update README to indicate that the build script takes a new option

that indicates if they are built statically or dynamically
  • Loading branch information...
1 parent 8e3a70d commit 2e19d2376f0f32178fb2f24fcb98e5b21b94ff79 @hungc hungc committed Jul 25, 2012
Showing with 3 additions and 3 deletions.
  1. +3 −3 README.md
View
@@ -27,15 +27,15 @@ Note: there a few unresolved test failures involving `Boost.Date_Time` and `Boos
1. Open a command prompt (building from Linux and Windows works; Mac has not been tested).
2. Execute bbndk-env.bat or bbndk-env.sh from root of NDK install.
3. Navigate to local boost repo.
-4. Change to the rim-build directory. Run the build.sh script using this command:
+4. Change to the rim-build directory. The build.sh script can build static or dynamic libraries. For example, to build dynamic libraries, use this command:
- ./build.sh install
+ ./build.sh install dynamic
This will invoke the bjam executable to build the libraries in subdirectories of bin.v2 as well as copy them to a staging directory (under rim-build/boost-stage).
All the libraries are compiled, not just the ported ones. The Boost.Python library can be enabled by setting the `PYTHON_SRC_DIR` variable in build.sh to the Python source location.
- Use `./build.sh clean` to clean the build.
+ Use `./build.sh clean <static|dynamic>` to clean the build.
## Test Instructions

0 comments on commit 2e19d23

Please sign in to comment.