This section pertains to:
- Detailed explanation of setting the
TARGETvariable, defined in previous sections as a way of controlling the build process. - Information on how targets and platforms are defined and handled by Theos.
%INDENT%
The system for which Theos is to build projects. Also defines miscellaneous build aspects.
Defaults and availability are platform-wise.
TARGET flags are split by colons (:), and different targets may parse these flags in different ways. The first flag is always used to define the target name, still.
For more information on how Theos' default targets handle flags, read Theos Default Targets. This document focuses on the behavior of Theos regarding targets.
Theos Targets should never directly read from TARGET. For more information, refer to _THEOS_TARGET_ARG_X.
%INDENTEND%
%INDENT%
Platforms are automatically picked by Theos through the output of uname -s (kernel name). For more information on this tool, refer to uname(1).
Each platform has a makefile included to define special behavior through variables. This makefile is placed at $(THEOS_MAKE_PATH)/platforms/<platform name>.mk.
These variables are described as follows. This section does not focus on the behavior defined by default Theos platforms. For such information, refer to Theos Default Platforms.
Defines whether Theos has loaded a platform.
Each platform should check for this value to be undefined before defining platform variables, and when doing so, it should set this variable to TRUE.
Defaults to empty.
The human-readable name of this platform, rather than the kernel name of the system.
Defaults to empty.
The default target for the platform to build to. Refer to Target Selection for more detail.
Defaults to empty.
The exclude flag for du(1).
Defaults to empty.
The name of the MD5 Sum generation program in the system.
Defaults to empty.
%INDENTEND%
%INDENT%
Targets are picked by Theos through the Target Name. The Target Name can be defined either on the platform (through the _THEOS_PLATFORM_DEFAULT_TARGET variable, or through the first flag of the TARGET variable.
Targets can be part of one of the following categories:
- Native: It describes the building process having as a target the same platform it's built at.
- Non-native: It describes the building process having as a target a different platform from the one it's built at.
Each target has a makefile included to define special behavior through variables. This makefile should be placed at $(THEOS_MAKE_PATH)/targets/<platform name>/<target name>.mk. Usually, platform target directories should contain a native.mk makefile symlinking to the native target.
These variables are defined as follows. This section does not focus on the behavior defined by default Theos platforms. For such information, refer to Theos Default Targets.
These variables should only be set by the target if they are previously undefined, otherwise the user's build configuration might be overriden.
Before defining these variables, check for _THEOS_TARGET_LOADED being undefined. They should only be set if this condition is true.
Some rules can also be defined or overriden in these makefiles.
(NOTE: In this context variables marked as system-wise are usually only to be written in this context, and should be considered read-only for other purposes.)
%INDENT%
Defines whether the target was loaded.
Should always be set to true on the start of the target Makefile.
Defaults to empty.
Defines the name of the target.
Should always be set.
Defaults to empty.
Defines the extension for binaries for the target.
Defaults to empty.
Defines the extension for libraries for the target.
Defaults to empty.
Defines the path of the C compiler for the target.
Defaults to empty.
Defines the path of the C++ compiler for the target.
Defaults to empty.
Defines the path of the linker for the target.
Should usually be set to the C++ compiler.
Defaults to empty.
Defines compiler flags specially from the target.
Defaults to empty.
The compiler flags to be applied when building a dynamic library for the target.
Defaults to empty.
????????
Defaults to empty.
Defines linker flags specially from the target.
Should contain -multiply_defined suppress.
Defaults to empty.
The linker flags to be applied when building a dynamic library for the target.
Defaults to empty.
Defines the path of the strip(1) tool.
Defaults to empty.
Defines the flags for the strip(1) tool.
Defaults to empty.
Defines the path for the codesign_allocate(1) tool.
Defaults to empty.
Defines the path for the codesigning tool.
It can be usually set to codesign(1) or ldid.
Defaults to empty.
Defines the flags for the codesigning tool.
Defaults to empty.
The path to private frameworks inside the sysroot.
Defaults to empty.
Defines the architecture of the output object files for the target.
Defaults to empty.
An unused variable.
Defaults to empty.
When creating a bundle with bundle.mk, the subdirectory where the Info.plist file will be placed.
Defaults to empty.
When creating a bundle with bundle.mk, the subdirectory where the bundle resources will be placed.
Defaults to empty.
When creating a bundle with bundle.mk, the subdirectory where the bundle main executable will be placed.
Defaults to empty.
%INDENTEND%
%INDENT%
These variables can be read by the target to suit itself to the project's needs.
Special variable name. Here, X is a number which starts on 1.
This variable can be used for querying the Xth flag of the TARGET variable, instead of directly parsing the TARGET variable.
This variable is empty if the Xth flag of TARGET is empty. Otherwise, it is filled with content.
This variable, if defined, specifies the desired system root for the target. Its data should then be considered when setting _THEOS_TARGET_CFLAGS and _THEOS_TARGET_LDFLAGS.
Defaults to empty.
%INDENTEND%
%INDENT%
When some target variables are common across targets (for instance, for all Windows targets, the executable extension will be .exe), by convention a makefile should be created at $(THEOS_MAKE_PATH)/targets/_common/<common name>.mk, and this makefile should be included by all targets that have this common variable.
The documentation of which common targets Theos offers and which target variables are usually placed there, refer to Default Common Targets.
%INDENTEND%
%INDENTEND%