static-cross-bins/include/_template.mak
2022-07-28 00:58:46 -04:00

64 lines
2.9 KiB
Makefile

NAME := example
EXAMPLE_VERSION := 1.2.3
# The download URL should point to a tar archive of some sort.
# On most systems, tar will handle most compression formats, so
# tar/gzip, tar/bzip2, etc, are fine. If the archive is in a different
# format, a recipe to create $(SRC) will need to be provided.
EXAMPLE_URL := https://example.com/releases/example-$(EXAMPLE_VERSION).tar.gz
# The list of all programs that the package builds.
# These targets can be called and built from the command line.
# If the package provides no programs, leave this list empty.
EXAMPLE_PROGRAMS := program-a program-b program-c
# The list of library names that the package builds.
# If the package provides no libraries, leave this list empty.
# Libraries will be represented as variables so that other packages may use them.
# For example, libsomething.a will be available as $$(libsomething).
EXAMPLE_LIBRARIES := libexample.a
# Allow the user to add any make, autoconf, or configure options that they want.
# Feel free to put any reasonable default values here.
EXAMPLE_CONFIG = --disable-unpopular-feature --disable-bulky-feature
# This creates the recipe chain that downloads, extracts, builds, and strips
# the binaries created by this package. This makes it so that only the main
# build recipe's contents need to be provided by the package author.
$(eval $(call create_recipes, \
$(NAME), \
$(EXAMPLE_VERSION), \
$(EXAMPLE_URL), \
$(EXAMPLE_PROGRAMS), \
$(EXAMPLE_LIBRARIES), \
))
# This is the main build recipe!
# Using $(BUILD_FLAG) as a target, it must compile the sources in $(SRC) and
# install the resulting programs and libraries into $(SYSROOT). If the package
# depends on any libraries, add their variable representations to this target's
# dependency list. For example, if the package depends on libsomething.a,
# add $$(libsomething) to $(BUILD_FLAG)'s dependencies.
$(BUILD_FLAG): $$(libz)
# This activates the cross-compiler toolchain by setting/exporting a lot of variables.
# Without this, builds would default to the system's compilers and libraries.
$(eval $(call activate_toolchain,$@))
# The configure step defines what features should be enabled for the program.
# If available, the --host and --prefix values should always be the values below.
# Try to only hard-code the flags that are critical to a successful static build.
# Optional flags should be put in EXAMPLE_CONFIG so the user can override them.
cd "$(SRC)" && ./configure \
$(CONFIGURE_DEFAULTS) \
--enable-static --disable-shared \
--with-zlib="$(SYSROOT)" \
$(EXAMPLE_CONFIG) \
CFLAGS="$(CFLAGS)" LDFLAGS="$(LDFLAGS)"
$(MAKE) -C "$(SRC)" clean
$(MAKE) -C "$(SRC)"
$(MAKE) -C "$(SRC)" install
# All programs should add themselves to the ALL_PROGRAMS list.
# ALL_PROGRAMS += $(EXAMPLE_PROGRAMS)
# Only programs that most users would want should be added to DEFAULT_PROGRAMS.
# DEFAULT_PROGRAMS += $(EXAMPLE_PROGRAMS)