From 1a3c4846190e5db562007656ecff99c7145f98af Mon Sep 17 00:00:00 2001 From: Chris Johns Date: Thu, 25 Apr 2013 15:05:16 +1000 Subject: Add a tip about using --dry-run before an initial build to check all is ok. --- doc/source-builder.txt | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/source-builder.txt b/doc/source-builder.txt index 1a11dc4..23c80b8 100644 --- a/doc/source-builder.txt +++ b/doc/source-builder.txt @@ -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 \ --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 \ --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 passing them on the command line using the `--macros` option. For RTEMS these -- cgit v1.2.3