rtems/rtems-source-builder
1
0
Fork 0
mirror of https://git.rtems.org/rtems-source-builder synced 2024-10-09 07:15:10 +08:00
Code Issues Packages Projects Releases Wiki Activity

Add a tip about using --dry-run before an initial build to check all is ok.

Browse Source
This commit is contained in:
Chris Johns 2013-04-25 15:05:16 +10:00
parent 9131a562ee
commit 1a3c484619
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source-builder.txt
View File

@ -1625,10 +1625,16 @@ and install them then build your tool set. The commands are:
------------------------------------------------------------- -------------------------------------------------------------
$ ../source-builder/sb-set-builder --log=l-4.11-at.txt \ $ ../source-builder/sb-set-builder --log=l-4.11-at.txt \
--prefix=$HOME/development/rtems/4.11 4.11/rtems-autotools --prefix=$HOME/development/rtems/4.11 4.11/rtems-autotools
$ export PATH=~/development/rtems/4.11/bin:$PATH $ export PATH=~/development/rtems/4.11/bin:$PATH <1>
$ ../source-builder/sb-set-builder --log=l-4.11-sparc.txt \ $ ../source-builder/sb-set-builder --log=l-4.11-sparc.txt \
--prefix=$HOME/development/rtems/4.11 4.11/rtems-sparc --prefix=$HOME/development/rtems/4.11 4.11/rtems-sparc
------------------------------------------------------------- -------------------------------------------------------------
<1> Setting the path.
TIP: If this is your first time building the tools and RTEMS it pays to add the
`--dry-run` option. This will run through all the configuration files and if
any checks fail you will see this quickly rather than waiting for until the
build fails a check.
To build snapshots for testing purposes you use the available macro maps To build snapshots for testing purposes you use the available macro maps
passing them on the command line using the `--macros` option. For RTEMS these passing them on the command line using the `--macros` option. For RTEMS these