2007-09-27 Joel Sherrill <joel.sherrill@oarcorp.com>

	* ChangeLog: New tests. Clean up. Rework so all tests use the same
	shared Makefile for the hard logic of producing an executable.
	* Makefile, Makefile.shared, README.Makefiles, networkconfig.h,
	rtems_init.c: New files.

1 files changed, 45 insertions, 0 deletions

diff --git a/README.Makefiles b/README.Makefiles
new file mode 100644
index 0000000..7d79cea
--- /dev/null
+++ b/README.Makefiles
@@ -0,0 +1,45 @@
+#
+# $Id$
+#
+
+The following is an example of how to build these Ada examples:
+
+export RTEMS_MAKEFILE_PATH=/home/joel/rtems-4.8-work/bsp-install/CPU-rtems4.8/BSP/
+make clean all
+
+This procedure has been used on the following BSPs:
+
+  arm/edb7312
+  bfin/eZKit533
+  i386/pc386 
+  m68k/mcf5206elite
+  mips/jmr3904
+  powerpc/gen5200
+  powerpc/psim
+  sparc/erc32
+  sparc/leon2
+  sparc/leon3
+  sparc/sis
+
+The Makefile directly produces an executable for a BSP which directly runs
+the format (usually ELF) produced by just linking an application.
+There are a couple of BSP families which require just a bit of
+assistance that this Makefile knows about -- gen5200 and pc386.
+The executables produced by this Makefile should run on at least the
+following BSPs:
+
++  arm/edb7312
++  i386/pc386
++  mips/jmr3904
++  powerpc/icecube
++  powerpc/psim
++  powerpc/score603e
++  sparc/erc32
++  sparc/leon2
++  sparc/leon3
+
+Some BSPs require even more manipulation of the ELF file before it can
+be run on the target hardware.  For example, the Freescale IceCube
+variant of the gen5200 BSP uses U-Boot and you have to run mkimage
+to get a bootable file.
+