source: examples-v2/README.waf @ 2c8ab41

Last change on this file since 2c8ab41 was 2c8ab41, checked in by Joel Sherrill <joel@…>, on Sep 24, 2018 at 10:33:53 PM

README.waf: Update waf URL and sis->erc32

  • Property mode set to 100644
File size: 1.9 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/4.11.
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/4.11.
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 'sparc/erc32' BSP:
32
33    $ waf configure --rtems=$HOME/Development/rtems/build/4.11 \
34                    --rtems-tools=$HOME/Development/rtems/4.11 \
35                    --rtems-bsps=sparc/erc32
36
37   You can use '--rtems-archs=sparc,i386' or
38   '--rtems-bsps=sparc/erc32,i386/pc586' to build for more than BSP at a time.
39
406. Build:
41
42   $ waf
43
447. Run the executable using the simulator:
45
46    $ $HOME/Development/rtems/4.11/bin/sparc-rtems4.11-run \
47       ./build/sparc-rtems4.11-sis/hello
48
49[1] It is good practice to keep your environment as empty as possible. Setting
50    paths to tools or specific values to configure or control builds is
51    dangerous because settings can leak between different builds and change
52    what you expect a build to do. The waf tool used here lets you specify on
53    the command line the tools and RTEMS paths and this is embedded in waf's
54    configuration information. If you have a few source trees working at any
55    one time with different tool sets or configurations you can easly move
56    between them safe in the knowledge that one build will not infect another.
57
58
Note: See TracBrowser for help on using the repository browser.