source: examples-v2/README.waf @ a5c981d

Last change on this file since a5c981d was a5c981d, checked in by Joel Sherrill <joel@…>, on Oct 14, 2018 at 8:40:49 PM

README.waf: Update to reflect RTEMS 5 and sis->erc32 transition

  • Property mode set to 100644
File size: 2.1 KB
Line 
1RTEMS Waf
2~~~~~~~~~
3
4You can find the Waf project here:
5
6 https://waf.io
7
8Simple instructions on How to set up Waf is here:
9
10 http://www.rtems.org/ftp/pub/rtems/people/chrisj/rtl/rtems-linker/waf.html
11
12Steps
13-----
14
151. Build or install the tools. In this example the path is
16   $HOME/Development/rtems/5.
17
182. Build and install the RTEMS Board Support Packages you want to use. In this
19   example the path is $HOME/Development/rtems/build/5.
20
213. Unpack this package somewhere, anywhere on your disk and change into the top
22   level directory.
23
244. Populate the git submodule:
25
26    $ git submodule init
27    $ git submodule update
28
295. Configure with your specific settings. In this case the path to the tools
30   and RTEMS and provided on the command line and so do not need to be in your
31   path or environment [1] and we limit the build to a single BSP. The single
32   BSP should be the 'sparc/erc32' BSP since this is the easiest BSP to use
33   on a simulator. After you have successfully build the executables for this
34   BSP and run them on the simulator, you can repeat this exercise with the
35   BSP you are most interested in.
36
37    $ waf configure --rtems=$HOME/Development/rtems/build/5 \
38                    --rtems-tools=$HOME/Development/rtems/5 \
39                    --rtems-bsps=sparc/erc32
40
41   You can use '--rtems-archs=sparc,i386' or
42   '--rtems-bsps=sparc/erc32,i386/pc586' to build for more than BSP at a time.
43
446. Build:
45
46   $ waf
47
487. Run the executable using the simulator:
49
50    $ $HOME/Development/rtems/5/bin/sparc-rtems5-run \
51       ./build/sparc-rtems5-sis/hello
52
53[1] It is good practice to keep your environment as empty as possible. Setting
54    paths to tools or specific values to configure or control builds is
55    dangerous because settings can leak between different builds and change
56    what you expect a build to do. The waf tool used here lets you specify on
57    the command line the tools and RTEMS paths and this is embedded in waf's
58    configuration information. If you have a few source trees working at any
59    one time with different tool sets or configurations you can easly move
60    between them safe in the knowledge that one build will not infect another.
61
62
Note: See TracBrowser for help on using the repository browser.