Make all BSPs use the same rules for invoking gcc and g++ to link an application. Share as much logic as possible for .num file and size information. Let BSPs provide custom rules to tranform executable from linked .exe to downloadable RTEMS Application Loadable File (RALF) .ralf file.

1 files changed, 4 insertions, 16 deletions

diff --git a/make/custom/mvme167.cfg b/make/custom/mvme167.cfg
index 0fb5253d9a..35e567354f 100644
--- a/make/custom/mvme167.cfg
+++ b/make/custom/mvme167.cfg
@@ -27,16 +27,9 @@ CPU_CFLAGS = -m68040
 # optimize flag: typically -O2
 CFLAGS_OPTIMIZE_V = -O2 -g -fno-omit-frame-pointer
 
-# Here is the rule to actually build a $(ARCH)/foo.exe
-# It also builds $(ARCH)/foo.nm
-# Usage ref: src/tests/sptest/sp1/Makefile
-#
 # We use TFTP to transfer files to the MVME167. We generate binary files
 # rather than S-records. We skip the header during downloads.
 
-# The following are definitions of make-exe which will work using ld as
-# is currently required.
-
 # The MC68040 does not implement all MC68881/MC68882 instructions, so use
 # either the gcc floating-point software support (msoft-float libraries), or
 # use the Motorola FPSP floating-point emulator in
@@ -47,13 +40,8 @@ CFLAGS_OPTIMIZE_V = -O2 -g -fno-omit-frame-pointer
 # in rtems/c/src/lib/libbsp/m68k/mvme167/startup/bststart.c in bsp_start().
 # Floating-point support will then be limited. See the mvme167 README file
 # for more details.
-define make-exe
-	$(LINK.c) $(AM_CFLAGS) $(AM_LDFLAGS) -o $(basename $@)_sym.exe \
-	    $(LINK_OBJS) $(LINK_LIBS)
-	$(NM) -g -n $(basename $@)_sym.exe > $(basename $@).nm
-	cp $(basename $@)_sym.exe $(basename $@).exe 
-	$(STRIP) $(basename $@).exe
-	$(SIZE) $(basename $@)_sym.exe
+define bsp-post-link
+	$(default-bsp-post-link)
+	cp $(basename $@)$(EXEEXT) $(basename $@)$(DOWNEXT)
+	$(STRIP) $(basename $@)$(DOWNEXT)
 endef
-
-# Miscellaneous additions go here