px4-firmware

dark0707

History

px4dev 0c43315c1e Hotfix: better error messages for missing modules		2013-05-13 22:20:08 -07:00
..
README.txt	Change the way modules are built so that object paths are relative and use vpath for locating sources (so source paths are also shorter).	2013-05-11 11:32:05 -07:00
board_px4fmu.mk	Merge working changes into export-build branch.	2013-04-26 16:14:32 -07:00
board_px4io.mk	Merge working changes into export-build branch.	2013-04-26 16:14:32 -07:00
config_px4fmu_default.mk	More example fixes	2013-05-13 08:28:36 +02:00
config_px4io_default.mk	Moved all drivers to new world, PX4IO completely in new world	2013-04-28 01:30:14 +02:00
firmware.mk	Hotfix: better error messages for missing modules	2013-05-13 22:20:08 -07:00
module.mk	Change the way modules are built so that object paths are relative and use vpath for locating sources (so source paths are also shorter).	2013-05-11 11:32:05 -07:00
nuttx.mk	Merge working changes into export-build branch.	2013-04-26 16:14:32 -07:00
setup.mk	Remove some naked command invocations.	2013-04-28 12:47:34 -07:00
toolchain_gnu-arm-eabi.mk	HOTFIX: simplify symbol names going into the ROMFS object, hopefully this avoids inconsistent symbol naming on Windows.	2013-05-12 14:04:57 -07:00
upload.mk	Remove some naked command invocations.	2013-04-28 12:47:34 -07:00

README.txt

PX4 Build System
================

The files in this directory implement the PX4 runtime firmware build system
and configuration for the standard PX4 boards and software, in conjunction
with Makefile in the parent directory.

../Makefile

	Top-level makefile for the PX4 build system. This makefile supports
	building NuttX archives, as well as supervising the building of all
	of the defined PX4 firmware configurations.

	Try 'make help' in the parent directory for documentation.

firmware.mk

	Manages the build for one specific firmware configuration. 
	See the comments at the top of this file for detailed documentation.

	Builds modules, builtin command lists and the ROMFS (if configured).

	This is the makefile directly used by external build systems; it can
	be configured to compile modules both inside and outside the PX4
	source tree. When used in this mode, at least BOARD, MODULES and 
	CONFIG_FILE must be set.

module.mk

	Called by firmware.mk to build individual modules.
	See the comments at the top of this file for detailed documentation.

	Not normally used other than by firmware.mk.

nuttx.mk

	Called by ../Makefile to build or download the NuttX archives.

upload.mk

	Called by ../Makefile to upload files to a target board. Can be used
	by external build systems as well.

setup.mk

	Provides common path and tool definitions. Implements host system-specific
	compatibility hacks.

board_<boardname>.mk

	Board-specific configuration for <boardname>. Typically sets CONFIG_ARCH
	and then includes the toolchain definition for the board.

config_<boardname>_<configname>.mk

	Parameters for a specific configuration on a specific board.
	The board name is derived from the filename.  Sets MODULES to select
	source modules to be included in the configuration, may also set
	ROMFS_ROOT to build a ROMFS and BUILTIN_COMMANDS to include non-module
	commands (e.g. from NuttX)

toolchain_<toolchainname>.mk

	Provides macros used to compile and link source files.
	Accepts EXTRADEFINES to add additional pre-processor symbol definitions,
	EXTRACFLAGS, EXTRACXXFLAGS, EXTRAAFLAGS and EXTRALDFLAGS to pass
	additional flags to the C compiler, C++ compiler, assembler and linker
	respectively.

	Defines the COMPILE, COMPILEXX, ASSEMBLE, PRELINK, ARCHIVE and LINK
	macros that are used elsewhere in the build system.