2
# Custom Makefile shell
4
# This file may be edited freely, since it will not be regenerated
5
# by the project manager.
7
# Use this makefile to define rules to make external binaries
8
# and deposit them in the $(EXTERNAL_BINARIES_DIR) directory.
10
# If you have specified external modules during your component
11
# creation, you will find make rules already in place below.
12
# You will likely have to edit these to suit your individual
15
# You may wish to use the CPU, BUILD_SPEC or TOOL make variables in
16
# your Makefile to support builds for different architectures. Use
17
# the FORCE_EXTERNAL_MAKE phony target to ensure that your external
20
# The example below assumes that your custom makefile is in the
21
# mySourceTree directory, and that the binary file it produces
22
# is placed into the $(BUILD_SPEC) sub-directory.
24
# EXTERNAL_SOURCE_BASE = /folk/me/mySourceTree
25
# EXTERNAL_MODULE = myLibrary.o
26
# EXTERNAL_MAKE = make
28
# $(EXTERNAL_BINARIES_DIR)/$(EXTERNAL_MODULE) : FORCE_EXTERNAL_MAKE
29
# $(EXTERNAL_MAKE) -C $(EXTERNAL_SOURCE_BASE) \
30
# -f $(EXTERNAL_SOURCE_BASE)/Makefile \
31
# CPU=$(CPU) BUILD_SPEC=$(BUILD_SPEC) $(@F)
32
# $(CP) $(subst /,$(DIRCHAR),$(EXTERNAL_SOURCE_BASE)/$(BUILD_SPEC)/$(@F) $@)
34
# If you are not adding your external modules from the component wizard,
35
# you will have to include them in your component yourself:
37
# From the GUI, you can do this with the Component's 'Add external module'
40
# If you are using the command line, add the module(s) by editing the
41
# MODULES line in component.cdf file, e.g.
43
# Component INCLUDE_MYCOMPONENT {
45
# MODULES foo.o goo.o \
50
# rules to build custom libraries