source: rtems/make/custom/mvme167.cfg @ 2d78d77

#
#  Config file for the mvme167 BSP 
#
#  $Id$
#

# THIS BSP USES ELF IMAGES. IT WILL NOT WORK WITH COFF UNLESS CHANGES
# ARE MADE TO THE LINKCMDS FILE.

RTEMS_CPU=m68k
RTEMS_CPU_MODEL=m68040

include $(RTEMS_ROOT)/make/custom/default.cfg

# This is the actual bsp directory used during the build process.
RTEMS_BSP_FAMILY=mvme167

#
#  This contains the compiler options necessary to select the CPU model
#  and (hopefully) optimize for it.  We also specify the BSP during compilation.
#  This should really get its own flag, but it works here.
#

CPU_CFLAGS = -m68040


# optimize flag: typically -O2
CFLAGS_OPTIMIZE_V = -O2 -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
#   rtems/c/src/lib/libcpu/m68k/m68040/fpsp
# The default is to use the FPSP. 
# To use the msoft-float libraries, uncomment the three lines below.
# You then should comment the M68KFPSPInstallExceptionHandlers() statement
# 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
endef

# Miscellaneous additions go here