180 |
180 |
181 bake works by downloading source packages into a source directory, |
181 bake works by downloading source packages into a source directory, |
182 and installing libraries into a build directory. bake can be run |
182 and installing libraries into a build directory. bake can be run |
183 by referencing the binary, but if one chooses to run bake from |
183 by referencing the binary, but if one chooses to run bake from |
184 outside of the directory it was downloaded into, it is advisable |
184 outside of the directory it was downloaded into, it is advisable |
185 to put bake into your path, such as follows (Linux bash shell example):: |
185 to put bake into your path, such as follows (Linux bash shell example). |
186 |
186 First, change into the 'bake' directory, and then set the following |
187 $ export BAKE_HOME=`pwd`/bake |
187 environment variables |
188 $ export PATH=$PATH:$BAKE_HOME |
188 |
189 $ export PYTHONPATH=$PYTHONPATH:$BAKE_HOME |
189 :: |
190 |
190 |
191 However, setting environment variables is not strictly necessary to |
191 $ export BAKE_HOME=`pwd` |
192 complete this tutorial, so we'll call bake directly by specifying the path |
192 $ export PATH=$PATH:$BAKE_HOME:$BAKE_HOME/build/bin |
193 to it in our shell commands. |
193 $ export PYTHONPATH=$PYTHONPATH:$BAKE_HOME:$BAKE_HOME/build/lib |
|
194 |
|
195 This will put the bake.py program into the shell's path, and will allow |
|
196 other programs to find executables and libraries created by bake. Although |
|
197 several bake use cases do not require setting PATH and PYTHONPATH as above, |
|
198 full builds of ns-3-allinone (with the optional packages) typically do. |
194 |
199 |
195 Step into the workspace directory and type the following into your shell:: |
200 Step into the workspace directory and type the following into your shell:: |
196 |
201 |
197 $ ./bake.py configure -e ns-3.20 |
202 $ ./bake.py configure -e ns-3.20 |
198 |
203 |