# Generated by Code Composer Studio

# Makefile for C:\CCStudio_v3.2\boards\dsk6455_v2\flashburn\FBTC645x\FBTC645x.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\flashburn\FBTC645x

# 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_CGENDIR)\include

DIR_2= $(TI_CGENDIR)\bin

SOURCE=FBCmd.c
SOURCE=FBTC645x.c
SOURCE=FBurnCmd.c
SOURCE=Link.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 FBCmd.obj
	-@del /F FBTC645x.obj
	-@del /F FBurnCmd.obj
	-@del /F FBTC645x.out

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

Debug: Debug_norecurse

Debug_norecurse: FBTC645x.out


makefile.Debug.fbs: 
	copy FBTC645x.out ..

FBCmd.obj: $(FRC) FBCmd.c FBCmd.h FBTC645x.h $(DIR_1)\stdio.h type.h 
	"$(DIR_2)\cl6x" -g -q -as -o3 -mi1 -ml3 -mv6400+ "FBCmd.c" 

FBTC645x.obj: $(FRC) FBTC645x.c FBCmd.h FBTC645x.h $(DIR_1)\stdio.h type.h 
	"$(DIR_2)\cl6x" -g -q -as -o3 -mi1 -ml3 -mv6400+ "FBTC645x.c" 

FBurnCmd.obj: $(FRC) FBurnCmd.c FBCmd.h FBTC645x.h $(DIR_1)\stdio.h type.h 
	"$(DIR_2)\cl6x" -g -q -as -o3 -mi1 -ml3 -mv6400+ "FBurnCmd.c" 

FBTC645x.out: $(FRC) FBCmd.obj FBTC645x.obj FBurnCmd.obj Link.cmd 
	-@echo -z -q -c -o"FBTC645x.out" -x -l"rts64plus.lib"> makefile.Debug.lkf
	-@echo "FBCmd.obj">> makefile.Debug.lkf
	-@echo "FBTC645x.obj">> makefile.Debug.lkf
	-@echo "FBurnCmd.obj">> makefile.Debug.lkf
	-@echo "Link.cmd">> makefile.Debug.lkf
	"$(DIR_2)\cl6x" -@"makefile.Debug.lkf"
	-@del /F makefile.Debug.lkf
	$(MAKE) $(MFLAGS) -f makefile makefile.Debug.fbs
