[multiio commit] add rtems_waf submodule

[Joel Sherrill]

Module:    multiio
Branch:    master
Commit:    bc7765f2cd9fd34878db475581b724472d178534
Changeset: http://git.rtems.org/multiio/commit/?id=bc7765f2cd9fd34878db475581b724472d178534

Author:    Chirayu Desai <cdesai at cyanogenmod.org>
Date:      Fri Jan  3 12:59:14 2014 +0530

add rtems_waf submodule

---

 .gitignore  |    4 ++++
 .gitmodules |    3 +++
 LICENSE.2   |   20 ++++++++++++++++++++
 README.waf  |   51 +++++++++++++++++++++++++++++++++++++++++++++++++++
 rtems_waf   |    1 +
 5 files changed, 79 insertions(+), 0 deletions(-)

diff --git a/.gitignore b/.gitignore
index 7d0ec5b..9de6ae0 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,7 @@
 o-optimize
 FilesystemImage
 FilesystemImage.[ch]
+*.pyc
+.lock-waf_*
+*~
+build/*
diff --git a/.gitmodules b/.gitmodules
new file mode 100644
index 0000000..c6ec105
--- /dev/null
+++ b/.gitmodules
@@ -0,0 +1,3 @@
+[submodule "rtems_waf"]
+	path = rtems_waf
+	url = git://git.rtems.org/chrisj/rtems_waf.git
diff --git a/LICENSE.2 b/LICENSE.2
new file mode 100644
index 0000000..d17fad3
--- /dev/null
+++ b/LICENSE.2
@@ -0,0 +1,20 @@
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+this list of conditions and the following disclaimer in the documentation
+and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
diff --git a/README.waf b/README.waf
new file mode 100644
index 0000000..000b980
--- /dev/null
+++ b/README.waf
@@ -0,0 +1,51 @@
+RTEMS Waf
+~~~~~~~~~
+
+You can find the Waf project here:
+
+ http://code.google.com/p/waf/
+
+Simple instructions on How to set up Waf is here:
+
+ http://www.rtems.org/ftp/pub/rtems/people/chrisj/rtl/rtems-linker/waf.html
+
+Steps
+-----
+
+1. Build or install the tools. In this example the path is
+   $HOME/Development/rtems/4.11.
+
+2. Build and install the RTEMS Board Support Packages you want to use. In this
+   example the path is $HOME/Development/rtems/build/4.11.
+
+3. Unpack this package somewhere, anywhere on your disk and change into the top
+   level directory.
+
+4. Populate the git submodule:
+
+    $ git submodule init
+    $ git submodule update
+
+5. Configure with your specific settings. In this case the path to the tools
+   and RTEMS and provided on the command line and so do not need to be in your
+   path or environment [1] and we limit the build to 'sparc/sis' BSP:
+
+    $ waf configure --rtems=$HOME/Development/rtems/build/4.11 \
+                    --rtems-tools=$HOME/Development/rtems/4.11 \
+                    --rtems-bsps=sparc/sis
+
+   You can use '--rtems-archs=sparc,i386' or
+   '--rtems-bsps=sparc/sis,i386/pc586' to build for more than BSP at a time.
+
+6. Build:
+
+   $ waf
+
+[1] It is good practice to keep your environment as empty as possible. Setting
+    paths to tools or specific values to configure or control builds is
+    dangerous because settings can leak between different builds and change
+    what you expect a build to do. The waf tool used here lets you specify on
+    the command line the tools and RTEMS paths and this is embedded in waf's
+    configuration information. If you have a few source trees working at any
+    one time with different tool sets or configurations you can easly move
+    between them safe in the knowledge that one build will not infect another.
diff --git a/rtems_waf b/rtems_waf
new file mode 160000
index 0000000..3d38f36
--- /dev/null
+++ b/rtems_waf
@@ -0,0 +1 @@
+Subproject commit 3d38f366b776c0bb5b57739ee5c64d7f4e857b9a