Changes between Version 1 and Version 2 of Developer/Multilib

Timestamp:

09/24/05 03:43:15 (19 years ago)

Author:

ChrisJohns

Comment:

Added the external BSP build. Thanks Ralf.

Developer/Multilib

@@ -53 +53 @@
   * Binary packages for 3rd party distributions.
 
-The BSP can be a separate package, and therefore a library, or it can be built into the application. There is little difference between either BSP code base. The issues are more related to configuration control.
+The BSP can be:
+
+ *  Part of the RTEMS source tree,
+ *  A separate package (a separate library),
+ *  Built into the application.
+
+Which type of BSP depends on where and how you use RTEMS and the type of hardware you use. If the target hardware is a common available platform placing the BSP in RTEMS is encouraged as others can share the work and aid fixing bugs.
+
+If the target hardware is custom built for a specific purpose placing that BSP into the RTEMS is not of great value unless it is the only one of that type for that processor and would make a good reference BSP. Making a separate BSP allows target hardware to be shared between applications. This is great for custom hardware a company uses in a number of products.
+
+Finally the BSP can be built into the application. This allows a separation from the released RTEMS sources, which has a slow release cycle, and a BSP specific to an application that has tight configuration control and verification and validation requirements.
+
+There can be little difference between BSP code base or it can be very different. A BSP separated from RTEMS does not require the BSP be merged and updated to work with a newer RTEMS release. RTEMS is always changing and evolving and RTEMS maintainers need the freedom to make changes that best suit RTEMS. On the other hand separate BSPs code not get to share common BSP code in RTEMS. The same extends to libchip drivers.
 
 The command line to build a CPU Kit for the M68K target can be -
 
-  $ ../rtems/configure --target=m68k-rtems \
+  $ ../rtems/configure --target=m68k-rtems4.7 \
                        --enable-multilib \
                        --enable-doc \
@@ -64 +76 @@
                        --enable-networking \
                        --disable-tests \
-                       --disable-itron
+                       --disable-itron \
+                       --prefix=/opt/rtems-4.7
 
 You will need to select the <tt>configure</tt> options that suite you. To build RTEMS enter -
 
-  $ make RTEMS_BSP="" all install
+  $ make RTEMS_BSP= all install
+= [wiki:BuildExternalBSP Building an External BSP] =
+
+
+Once you have a CPU Kit install you can build a BSP in the RTEMS source tree by using the following -
+
+  $ rm -rf ../rtems/cpukit
+  $ ../rtems/configure --target=m68k-rtems4.7 \
+                       --prefix=/opt/rtems-4.7
+  $ make RTEMS_BSP=xxxx