dark0707
/
px4-firmware
forked from Archive/PX4-Autopilot
1
0
Fork 0
Code Pull Requests Activity
px4-firmware/makefiles/firmware.mk

219 lines
6.1 KiB
Makefile
Raw Normal View History

Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
#
# Generic Makefile for PX4 firmware.
#
# Currently this assumes that we're just compiling SRCS
# and then linking the whole thing together.
#
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
# Requires:
#
# PLATFORM
# Must be set to a platform name known to the PX4 distribution.
#
# Optional:
#
# PX4_BASE:
# Points to a PX4 distribution. Normally determined based on the
# path to this file.
#
# CONFIG:
# Used to set the output filename; defaults to 'firmware'.
#
# WORK_DIR:
# Sets the directory in which the firmware will be built. Defaults
# to the directory 'build' under the directory containing the
# parent Makefile.
#
################################################################################
# Paths and configuration
################################################################################
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
#
# Work out where this file is, so we can find other makefiles in the
# same directory.
#
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
# If PX4_BASE wasn't set previously, work out what it should be
# and set it here now.
Recover commits lost in the previous merge. Syllableise PX4_BASE like its peers.
2013-01-16 22:23:49 -04:00
#
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
export PX4_MK_INCLUDE ?= $(dir $(lastword $(MAKEFILE_LIST)))
Recover commits lost in the previous merge. Syllableise PX4_BASE like its peers.
2013-01-16 22:23:49 -04:00
ifeq ($(PX4_BASE),)
export PX4_BASE := $(abspath $(PX4_MK_INCLUDE)/..)
endif
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
$(info %% PX4_BASE $(PX4_BASE))
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
#
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
# If WORK_DIR is not set, create a 'build' directory next to the
# parent Makefile.
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
#
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
PARENT_MAKEFILE := $(lastword $(filter-out $(lastword $(MAKEFILE_LIST)),$(MAKEFILE_LIST)))
ifeq ($(WORK_DIR),)
export WORK_DIR := $(dir $(PARENT_MAKEFILE))/build
endif
$(info %% WORK_DIR $(WORK_DIR))
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
#
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
# Paths
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
#
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
export NUTTX_SRC = $(PX4_BASE)/nuttx
export NUTTX_APPS = $(PX4_BASE)/apps
export MAVLINK_SRC = $(PX4_BASE)/mavlink
export ROMFS_SRC = $(PX4_BASE)/ROMFS
export IMAGE_DIR = $(PX4_BASE)/Images
export BUILD_DIR = $(PX4_BASE)/Build
export ARCHIVE_DIR = $(PX4_BASE)/Archives
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
#
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
# Extra tools.
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
#
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
# XXX should be in a common toolchain config somewhere.
#
MKFW = $(PX4_BASE)/Tools/px_mkfw.py
UPLOADER = $(PX4_BASE)/Tools/px_uploader.py
COPY = cp
REMOVE = rm -f
RMDIR = rm -rf
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
#
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
# Sanity-check the PLATFORM variable and then get the platform config.
#
# The platform config in turn will fetch the toolchain configuration.
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
#
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
ifeq ($(PLATFORM),)
$(error The PLATFORM variable must be set before including firmware.mk)
endif
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
include $(PX4_MK_INCLUDE)/$(PLATFORM).mk
#
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
# Makefile debugging.
#
Q := $(if $(V),,@)
#
# Host-specific paths, hacks and fixups
#
SYSTYPE := $(shell uname -s)
ifeq ($(SYSTYPE),Darwin)
# Eclipse may not have the toolchain on its path.
export PATH := $(PATH):/usr/local/bin
endif
#
# Serial port defaults.
#
# XXX The uploader should be smarter than this.
#
ifeq ($(SYSTYPE),Darwin)
SERIAL_PORTS ?= "/dev/tty.usbmodemPX1,/dev/tty.usbmodemPX2,/dev/tty.usbmodemPX3,/dev/tty.usbmodemPX4,/dev/tty.usbmodem1,/dev/tty.usbmodem2,/dev/tty.usbmodem3,/dev/tty.usbmodem4"
endif
ifeq ($(SYSTYPE),Linux)
SERIAL_PORTS ?= "/dev/ttyACM5,/dev/ttyACM4,/dev/ttyACM3,/dev/ttyACM2,/dev/ttyACM1,/dev/ttyACM0"
endif
ifeq ($(SERIAL_PORTS),)
SERIAL_PORTS = "\\\\.\\COM32,\\\\.\\COM31,\\\\.\\COM30,\\\\.\\COM29,\\\\.\\COM28,\\\\.\\COM27,\\\\.\\COM26,\\\\.\\COM25,\\\\.\\COM24,\\\\.\\COM23,\\\\.\\COM22,\\\\.\\COM21,\\\\.\\COM20,\\\\.\\COM19,\\\\.\\COM18,\\\\.\\COM17,\\\\.\\COM16,\\\\.\\COM15,\\\\.\\COM14,\\\\.\\COM13,\\\\.\\COM12,\\\\.\\COM11,\\\\.\\COM10,\\\\.\\COM9,\\\\.\\COM8,\\\\.\\COM7,\\\\.\\COM6,\\\\.\\COM5,\\\\.\\COM4,\\\\.\\COM3,\\\\.\\COM2,\\\\.\\COM1,\\\\.\\COM0"
endif
################################################################################
# NuttX libraries and paths
################################################################################
#
# Check that the NuttX archive for the selected platform is available.
#
NUTTX_ARCHIVE := $(wildcard $(ARCHIVE_DIR)/$(PLATFORM).export)
ifeq ($(NUTTX_ARCHIVE),)
$(error The NuttX export archive for $(PLATFORM) is missing from $(ARCHIVE_DIR) - try 'make archives' in $(PX4_BASE))
endif
#
# The NuttX config header should always be present in the NuttX archive, and
# if it changes, everything should be rebuilt. So, use it as the trigger to
# unpack the NuttX archive.
#
NUTTX_EXPORT_DIR = $(WORK_DIR)/nuttx-export
NUTTX_CONFIG_HEADER = $(NUTTX_EXPORT_DIR)/include/nuttx/config.h
#
# Use the linker script from the NuttX export
#
LDSCRIPT = $(NUTTX_EXPORT_DIR)/build/ld.script
#
# Add directories from the NuttX export to the relevant search paths
#
INCLUDE_DIRS += $(NUTTX_EXPORT_DIR)/include
LIB_DIRS += $(NUTTX_EXPORT_DIR)/libs
LIBS += -lapps -lnuttx
LINK_DEPS += $(wildcard $(addsuffix /*.a,$(LIB_DIRS)))
################################################################################
# Build rules
################################################################################
#
# Things that, if they change, might affect everything
#
GLOBAL_DEPS += $(MAKEFILE_LIST) $(NUTTX_CONFIG_HEADER)
#
# What we're going to build.
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
#
Recover commits lost in the previous merge. Syllableise PX4_BASE like its peers.
2013-01-16 22:23:49 -04:00
PRODUCT_BUNDLE = $(WORK_DIR)/firmware.px4
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
PRODUCT_BIN = $(WORK_DIR)/firmware.bin
PRODUCT_SYM = $(WORK_DIR)/firmware.sym
.PHONY: all
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
all: $(PRODUCT_BUNDLE)
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
#
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
# Object files we will generate from sources
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
#
OBJS = $(foreach src,$(SRCS),$(WORK_DIR)/$(src).o)
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
#
# Rules
#
$(filter %.c.o,$(OBJS)): $(WORK_DIR)/%.c.o: %.c $(GLOBAL_DEPS)
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
@mkdir -p $(dir $@)
$(call COMPILE,$<,$@)
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
$(filter %.cpp.o,$(OBJS)): $(WORK_DIR)/%.cpp.o: %.cpp $(GLOBAL_DEPS)
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
@mkdir -p $(dir $@)
$(call COMPILEXX,$<,$@)
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
$(filter %.S.o,$(OBJS)): $(WORK_DIR)/%.S.o: %.S $(GLOBAL_DEPS)
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
@mkdir -p $(dir $@)
$(call ASSEMBLE,$<,$@)
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
$(NUTTX_CONFIG_HEADER): $(NUTTX_ARCHIVE)
@echo %% Unpacking $(NUTTX_ARCHIVE)
$(Q) unzip -q -o -d $(WORK_DIR) $(NUTTX_ARCHIVE)
$(Q) touch $@
$(PRODUCT_BUNDLE): $(PRODUCT_BIN)
@echo %% Generating $@
$(Q) $(MKFW) --prototype $(IMAGE_DIR)/$(PLATFORM).prototype \
--git_identity $(PX4_BASE) \
--image $< > $@
Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.
2013-01-06 01:46:50 -04:00
$(PRODUCT_BIN): $(PRODUCT_SYM)
$(call SYM_TO_BIN,$<,$@)
$(PRODUCT_SYM): $(OBJS) $(GLOBAL_DEPS) $(LINK_DEPS)
$(call LINK,$@,$(OBJS))
Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. Pass the platform define into the firmware builder.
2013-01-17 01:03:27 -04:00
upload: $(PRODUCT_BUNDLE) $(UPLOADER)
@python -u $(UPLOADER) --port $(SERIAL_PORTS) $(PRODUCT_BUNDLE)
clean:
@echo %% cleaning
$(Q) $(REMOVE) $(PRODUCT_BUNDLE) $(PRODUCT_BIN) $(PRODUCT_SYM)
$(Q) $(REMOVE) $(OBJS) $(DEP_INCLUDES)
$(Q) $(RMDIR) $(NUTTX_EXPORT_DIR)
#
# DEP_INCLUDES is defined by the toolchain include in terms of $(OBJS)
#
-include $(DEP_INCLUDES)