makefile

it is programed on dsk6455,and it describe the use of the LED module of the the dsk6455 Board Suppor

# Generated by Code Composer Studio

# Makefile for C:\CCStudio_v3.2\boards\dsk6455_v2\examples\led\led.pjt
# This makefile is intended to be compatible with any version of make.
#
# USAGE
# Step 1: Set up proper environment variables, by running DosRun.bat
#         (Windows platform) or set them up by yourself.
# Step 2: Change directory to the directory of this makefile, which is stored
#         in the macro MAKEFILE_DIR
# Step 3: In the makefile directory, you can perform one of these operations:
#         To build the configuration <config>, type make <config>
#         To clean the configuration <config>, type make <config>clean
#         To rebuild the configuration <config>, type make <config>rebuild
#         If <config> is not specified, the operations apply to the active
#         configuration, which is stored in the macro ACTIVE_CONFIG.
# For CCS gmake users: In the makefile directory, you can perform one of these operations:
#         To build the configuration <config>, type gmake projectName.mak <config>
#         To clean the configuration <config>, type gmake <config>clean
#         To rebuild the configuration <config>, type gmake <config>rebuild
#         If <config> is not specified, the operations apply to the active
#         configuration, which is stored in the macro ACTIVE_CONFIG.
#
# DETAILS
# Step 1:
#   In order for this makefile to work, you must have the environment variables
# set properly.  Specifically, the paths to build programs and the system-wide
# header files and library files must be set.
#   In Windows, a batch file "DosRun.bat", located at the root directory of
# the Code Composer Studio installation, is provided to set up these variables.
#   In UNIX, you can set up these environment variables yourself.  The "PATH"
# variable must include the paths to the build programs, and the "C_DIR" and
# "A_DIR" variables must include the paths to the system-wide header files and
# library files.
#
# Step 2:
#   System files referenced by this project are specified in full path names,
# while other files in this project are specified in path names relative to the
# directory of this makefile.  These directory names are stored in DIR_x macros.
# You can modify them to reflect the locations of the files on this system.
#   It is important that the command to make this makefile is issued from the
# directory of this makefile, which is stored in the macro MAKEFILE_DIR.
#
# Step 3:
#   There are three operations that can be performed on a build configuration:
# make, clean, and rebuild. A rebuild forces all files in the configuration to
# be rebuilt.
# To build the configuration <config>, type make <config>
# To clean the configuration <config>, type make <config>clean
# To rebuild the configuration <config>, type make <config>rebuild
#   If <config> is not specified, the operations apply to the active
# configuration. The active configuration can be any valid build configuration
# (including "all") and is specified in the macro ACTIVE_CONFIG.
# To build the active configuration, type make
# To clean the active configuration, type make clean
# To rebuild the active configuration, type make rebuild
#
# For CCS gmake users:
#   There are three operations that can be performed on a build configuration:
# make, clean, and rebuild. A rebuild forces all files in the configuration to
# be rebuilt.
# To build the configuration <config>, type gmake projectName.mak <config>
# To clean the configuration <config>, type gmake <config>clean
# To rebuild the configuration <config>, type gmake <config>rebuild
#   If <config> is not specified, the operations apply to the active
# configuration. The active configuration can be any valid build configuration
# (including "all") and is specified in the macro ACTIVE_CONFIG.
# To build the active configuration, type gmake
# To clean the active configuration, type gmake clean
# To rebuild the active configuration, type gmake rebuild

# The MKFLAGS macro takes the place of the MFLAGS or MAKEFLAGS macro. If it
# gives you any trouble, just delete the macro. It is used when recursively
# calling make (i.e. when rebuilding)
MKFLAGS= $(MFLAGS)$(MAKEFLAGS)

MAKEFILE_DIR= $(TI_DIR)\boards\dsk6455_v2\examples\led

# The active configuration can be one of these valid build configurations:
# all, Debug
ACTIVE_CONFIG= Debug

# These DIR_x macros store the directories of the files used in this project.
# There must be no trailing spaces after these macros.

DIR_1= $(TI_BIOSDIR)\xdctools

DIR_2= Debug

DIR_3= ..\..\include

DIR_4= $(TI_BIOSDIR)\packages\ti\bios\include

DIR_5= $(TI_CGENDIR)\include

DIR_6= $(TI_CGENDIR)\bin

SOURCE=led.c
SOURCE=led.tcf
SOURCE=linker.cmd

active_config: $(ACTIVE_CONFIG)

norecurse: $(ACTIVE_CONFIG)_norecurse

clean: $(ACTIVE_CONFIG)clean

clean_norecurse: $(ACTIVE_CONFIG)clean_norecurse

rebuild: $(ACTIVE_CONFIG)rebuild

force_rebuild: 

all: Debug 

allclean: Debugclean 

allrebuild: Debugrebuild 


Debugclean: Debugclean_norecurse

Debugclean_norecurse: 
	-@del /F ledcfg.h
	-@del /F ledcfg.h62
	-@del /F ledcfg.s62
	-@del /F ledcfg_c.c
	-@del /F $(DIR_2)\led.obj
	-@del /F $(DIR_2)\ledcfg.obj
	-@del /F $(DIR_2)\ledcfg_c.obj
	-@del /F $(DIR_2)\led.out

Debugrebuild: 
	$(MAKE) $(MFLAGS) -f makefile Debug FRC=force_rebuild

Debug: Debug_norecurse

Debug_norecurse: $(DIR_2)\led.out



ledcfg.h \
ledcfg.h62 \
ledcfg.s62 \
ledcfg_c.c: $(FRC) led.tcf 
	"$(DIR_1)\tconf" -b -Dconfig.importPath="$(TI_BIOSDIR)/packages;" led.tcf

$(DIR_2)\led.obj: $(FRC) led.c $(DIR_3)\dsk6455.h $(DIR_3)\dsk6455_dip.h $(DIR_3)\dsk6455_led.h ledcfg.h $(DIR_4)\std.h $(DIR_5)\stdio.h $(DIR_4)\sys.h $(DIR_4)\hst.h $(DIR_4)\log.h $(DIR_4)\sts.h $(DIR_4)\swi.h $(DIR_4)\tsk.h 
	"$(DIR_6)\cl6x" -g -fr"$(MAKEFILE_DIR)/Debug" -i"../../include/" -d"_DEBUG" -mr1 -mv6400+ --mem_model:data=far "led.c" 

$(DIR_2)\ledcfg.obj: $(FRC) ledcfg.s62 $(DIR_4)\buf.h62 $(DIR_4)\clk.h62 $(DIR_4)\confbeg.s62 $(DIR_4)\confend.s62 $(DIR_4)\dev.h62 $(DIR_4)\dgn.h62 $(DIR_4)\dhl.h62 $(DIR_4)\dio.h62 $(DIR_4)\dpi.h62 $(DIR_4)\ecm.h62 $(DIR_4)\gbl.h62 $(DIR_4)\gio.h62 $(DIR_4)\hook.h62 $(DIR_4)\hst.h62 $(DIR_4)\hwi.h62 $(DIR_4)\idl.h62 $(DIR_4)\isrc.h62 $(DIR_4)\lck.h62 ledcfg.h62 $(DIR_4)\log.h62 $(DIR_4)\mbx.h62 $(DIR_4)\mem.h62 $(DIR_4)\msgq.h62 $(DIR_4)\obj.h62 $(DIR_4)\pip.h62 $(DIR_4)\pool.h62 $(DIR_4)\prd.h62 $(DIR_4)\que.h62 $(DIR_4)\rtdx.h62 $(DIR_4)\sem.h62 $(DIR_4)\sio.h62 $(DIR_4)\sts.h62 $(DIR_4)\swi.h62 $(DIR_4)\sys.h62 $(DIR_4)\tsk.h62 $(DIR_4)\udev.h62 $(DIR_4)\std.h62 
	"$(DIR_6)\cl6x" -g -fr"$(MAKEFILE_DIR)/Debug" -i"../../include/" -d"_DEBUG" -mr1 -mv6400+ --mem_model:data=far "ledcfg.s62" 

$(DIR_2)\ledcfg_c.obj: $(FRC) ledcfg_c.c ledcfg.h $(DIR_4)\hst.h $(DIR_4)\log.h $(DIR_4)\std.h $(DIR_4)\sts.h $(DIR_4)\swi.h $(DIR_4)\tsk.h 
	"$(DIR_6)\cl6x" -g -fr"$(MAKEFILE_DIR)/Debug" -i"../../include/" -d"_DEBUG" -mr1 -mv6400+ --mem_model:data=far "ledcfg_c.c" 

$(DIR_2)\led.out: $(FRC) linker.cmd $(DIR_2)\led.obj $(DIR_2)\ledcfg.obj $(DIR_2)\ledcfg_c.obj 
	-@echo -z -c -m"./Debug/led.map" -o"./Debug/led.out" -w -x -l"../../lib/dsk6455bsl.lib"> makefile.Debug.lkf
	-@echo "linker.cmd">> makefile.Debug.lkf
	-@echo "$(DIR_2)\led.obj">> makefile.Debug.lkf
	-@echo "$(DIR_2)\ledcfg.obj">> makefile.Debug.lkf
	-@echo "$(DIR_2)\ledcfg_c.obj">> makefile.Debug.lkf
	"$(DIR_6)\cl6x" -@"makefile.Debug.lkf"
	-@del /F makefile.Debug.lkf