mcu
/
libopencm3
mirror of https://github.com/libopencm3/libopencm3.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2874 Commits
2 Branches
1 Tag
21 MiB
Branch: master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
libopencm3/mk/README

122 lines
4.0 KiB
Raw Permalink Normal View History

[BUILD] Add build system module makefiles, add README how to use it.
11 years ago
-------------------------------------------------------------------------------
README
-------------------------------------------------------------------------------
This directory contains makefile modular support files, that can be used in
your project.
Each module is packaged with two inclusion makefiles, <module>-config.mk and
<module>-rules.mk. The first one defines some new variables for the make, or
appends values to the existing variables for the make. The second defines rules
for support building.
So in your project, the <module>-config.mk should be included at some place,
where you are defining variables (near the beginning of the file), and file
<module>-rules.mk should be included in the rules part of makefile (somewhere
near to the end of file).
mk/genlink: change devices.data format to remove gcc specific options As discussed with karlp on irc the devices.data file should not contain gcc specific command line options. For that reason the command line options for gcc are now generated from the variables CPU and FPU by the rules in the mk directory. This breaks the genlink tests. genlink: simplified devices.data devices.data already had the information about the family name. By using the first field (by the pattern used to match it) as family name information that data doesn&#39;t have to be provided explicitly. The same data is used to generate the CPPFLAGS, such as -DSTM32F1 The architectures block of the devices.data file was redundant. genlink-config.mk uses family and subfamily to figure out which libopencm3 variant actually exists.
9 years ago
Example makefile using the gcc compiler module together with the linker script
generator module:
[BUILD] Add build system module makefiles, add README how to use it.
11 years ago
>>>>>>
mk/genlink: change devices.data format to remove gcc specific options As discussed with karlp on irc the devices.data file should not contain gcc specific command line options. For that reason the command line options for gcc are now generated from the variables CPU and FPU by the rules in the mk directory. This breaks the genlink tests. genlink: simplified devices.data devices.data already had the information about the family name. By using the first field (by the pattern used to match it) as family name information that data doesn&#39;t have to be provided explicitly. The same data is used to generate the CPPFLAGS, such as -DSTM32F1 The architectures block of the devices.data file was redundant. genlink-config.mk uses family and subfamily to figure out which libopencm3 variant actually exists.
9 years ago
DEVICE =
OPENCM3_DIR =
OBJS += foo.o
[BUILD] Add build system module makefiles, add README how to use it.
11 years ago
mk/genlink: change devices.data format to remove gcc specific options As discussed with karlp on irc the devices.data file should not contain gcc specific command line options. For that reason the command line options for gcc are now generated from the variables CPU and FPU by the rules in the mk directory. This breaks the genlink tests. genlink: simplified devices.data devices.data already had the information about the family name. By using the first field (by the pattern used to match it) as family name information that data doesn&#39;t have to be provided explicitly. The same data is used to generate the CPPFLAGS, such as -DSTM32F1 The architectures block of the devices.data file was redundant. genlink-config.mk uses family and subfamily to figure out which libopencm3 variant actually exists.
9 years ago
CFLAGS += -Os -ggdb3
CPPFLAGS += -MD
LDFLAGS += -static -nostartfiles
LDLIBS += -Wl,--start-group -lc -lgcc -lnosys -Wl,--end-group
[BUILD] Add build system module makefiles, add README how to use it.
11 years ago
mk/genlink: change devices.data format to remove gcc specific options As discussed with karlp on irc the devices.data file should not contain gcc specific command line options. For that reason the command line options for gcc are now generated from the variables CPU and FPU by the rules in the mk directory. This breaks the genlink tests. genlink: simplified devices.data devices.data already had the information about the family name. By using the first field (by the pattern used to match it) as family name information that data doesn&#39;t have to be provided explicitly. The same data is used to generate the CPPFLAGS, such as -DSTM32F1 The architectures block of the devices.data file was redundant. genlink-config.mk uses family and subfamily to figure out which libopencm3 variant actually exists.
9 years ago
include $(OPENCM3_DIR)/mk/genlink-config.mk
[BUILD] Add build system module makefiles, add README how to use it.
11 years ago
include $(OPENCM3_DIR)/mk/gcc-config.mk
.PHONY: clean all
mk/genlink: change devices.data format to remove gcc specific options As discussed with karlp on irc the devices.data file should not contain gcc specific command line options. For that reason the command line options for gcc are now generated from the variables CPU and FPU by the rules in the mk directory. This breaks the genlink tests. genlink: simplified devices.data devices.data already had the information about the family name. By using the first field (by the pattern used to match it) as family name information that data doesn&#39;t have to be provided explicitly. The same data is used to generate the CPPFLAGS, such as -DSTM32F1 The architectures block of the devices.data file was redundant. genlink-config.mk uses family and subfamily to figure out which libopencm3 variant actually exists.
9 years ago
all: binary.elf binary.hex
[BUILD] Add build system module makefiles, add README how to use it.
11 years ago
clean:
mk/genlink: change devices.data format to remove gcc specific options As discussed with karlp on irc the devices.data file should not contain gcc specific command line options. For that reason the command line options for gcc are now generated from the variables CPU and FPU by the rules in the mk directory. This breaks the genlink tests. genlink: simplified devices.data devices.data already had the information about the family name. By using the first field (by the pattern used to match it) as family name information that data doesn&#39;t have to be provided explicitly. The same data is used to generate the CPPFLAGS, such as -DSTM32F1 The architectures block of the devices.data file was redundant. genlink-config.mk uses family and subfamily to figure out which libopencm3 variant actually exists.
9 years ago
$(Q)$(RM) -rf binary.* *.o
[BUILD] Add build system module makefiles, add README how to use it.
11 years ago
mk/genlink: change devices.data format to remove gcc specific options As discussed with karlp on irc the devices.data file should not contain gcc specific command line options. For that reason the command line options for gcc are now generated from the variables CPU and FPU by the rules in the mk directory. This breaks the genlink tests. genlink: simplified devices.data devices.data already had the information about the family name. By using the first field (by the pattern used to match it) as family name information that data doesn&#39;t have to be provided explicitly. The same data is used to generate the CPPFLAGS, such as -DSTM32F1 The architectures block of the devices.data file was redundant. genlink-config.mk uses family and subfamily to figure out which libopencm3 variant actually exists.
9 years ago
include $(OPENCM3_DIR)/mk/genlink-rules.mk
include $(OPENCM3_DIR)/mk/gcc-rules.mk
[BUILD] Add build system module makefiles, add README how to use it.
11 years ago
<<<<<<
MODULES
=======
-------------------------------------------------------------------------------
gcc
-------------------------------------------------------------------------------
This module adds an extended support for GCC toolchain. This adds rules,
Fix misspellings using codespell tool
9 years ago
necessary for compiling C and C++ files into elf binary, and rules for
[BUILD] Add build system module makefiles, add README how to use it.
11 years ago
generation of bin, hex, or srec output files for flashing.
Variables to control the build process (should be set in your makefile):
------------------------------------------------------------------------
CFLAGS C compiler flags
CXXFLAGS C++ compiler flags
CPPFLAGS C preprocessor flags (used for C and for C++ compiler)
LDFLAGS Linker flags
ARCH_FLAGS Architecture specification flags (-mcpu, -march etc )
Variables to tell gcc about project dependencies and input files
----------------------------------------------------------------
LDSCRIPT Linker script file name (can be generated or fixed)
treewide: Fix some typos
3 years ago
LIBDEPS Array of library filenames that should be rebuilt if needed
[BUILD] Add build system module makefiles, add README how to use it.
11 years ago
LDLIBS Array of libraries to be linked with (array of -l<libname>)
OBJS Array of object files to be built
* [BUILD] Add build system module GENLINK, update README how to use it.
11 years ago
-------------------------------------------------------------------------------
genlink
-------------------------------------------------------------------------------
This module adds an support for the user to the linker script generator. The
linker script will be generated as the file $(DEVICE).ld in the project folder,
mk/genlink: change devices.data format to remove gcc specific options As discussed with karlp on irc the devices.data file should not contain gcc specific command line options. For that reason the command line options for gcc are now generated from the variables CPU and FPU by the rules in the mk directory. This breaks the genlink tests. genlink: simplified devices.data devices.data already had the information about the family name. By using the first field (by the pattern used to match it) as family name information that data doesn&#39;t have to be provided explicitly. The same data is used to generate the CPPFLAGS, such as -DSTM32F1 The architectures block of the devices.data file was redundant. genlink-config.mk uses family and subfamily to figure out which libopencm3 variant actually exists.
9 years ago
and automatically be used for the linking process.
Additionally the matching library is added to the LDLIBS variable.
* [BUILD] Add build system module GENLINK, update README how to use it.
11 years ago
Variables to control the build process (should be set in your makefile):
------------------------------------------------------------------------
DEVICE The full device part name used for the compilation process.
OPENCM3_DIR The root path of libopencm3 library.
Output variables from this module:
----------------------------------
mk/genlink: change devices.data format to remove gcc specific options As discussed with karlp on irc the devices.data file should not contain gcc specific command line options. For that reason the command line options for gcc are now generated from the variables CPU and FPU by the rules in the mk directory. This breaks the genlink tests. genlink: simplified devices.data devices.data already had the information about the family name. By using the first field (by the pattern used to match it) as family name information that data doesn&#39;t have to be provided explicitly. The same data is used to generate the CPPFLAGS, such as -DSTM32F1 The architectures block of the devices.data file was redundant. genlink-config.mk uses family and subfamily to figure out which libopencm3 variant actually exists.
9 years ago
CPPFLAGS (appended)
- Appends the chip family to the CPPFLAGS. For example -DSTM32F1
- Appends the include path for libopencm3
* [BUILD] Add build system module GENLINK, update README how to use it.
11 years ago
ARCH_FLAGS (replaced)
- Architecture build flags for specified chip.
* No needed to handle this variable if you use module <gcc> too.
LDSCRIPT (replaced)
- Linker script generated file.
* No needed to handle this variable if you use module <gcc> too.
mk/genlink: change devices.data format to remove gcc specific options As discussed with karlp on irc the devices.data file should not contain gcc specific command line options. For that reason the command line options for gcc are now generated from the variables CPU and FPU by the rules in the mk directory. This breaks the genlink tests. genlink: simplified devices.data devices.data already had the information about the family name. By using the first field (by the pattern used to match it) as family name information that data doesn&#39;t have to be provided explicitly. The same data is used to generate the CPPFLAGS, such as -DSTM32F1 The architectures block of the devices.data file was redundant. genlink-config.mk uses family and subfamily to figure out which libopencm3 variant actually exists.
9 years ago
LDLIBS (appended)
- LDLIBS += -lopencm3_$(family) is appended to link against the
matching library.
LDFLAGS (appended)
- LDFLAGS += -L$(OPENCM3_DIR)/lib is appended to make sure the
matching library can be found.
family,cpu,fpu (replaced)
- these are used internally to create the above variables
* [BUILD] Add build system module GENLINK, update README how to use it.
11 years ago
Temporary variables that you should not use in your makefile:
-------------------------------------------------------------
GENLINK_DEFS
GENLINK_ARCH
GENLINK_LIB