Lines Matching refs:a
5 The CHRE build system is based on Make, and uses a set of Makefiles that allow
6 building the CHRE framework for a variety of hardware and software architectures
9 recommended), by abstracting out key operations to a few Make or environment
17 By default, the output of the build is linked into both a static archive
18 `libchre.a` and a shared library `libchre.so`, though generally only one of the
23 The CHRE build system was originally designed around the philosophy that a
26 build system for multi-threaded builds and also promotes a level of separation
36 linker flags are compatible with all toolchains. For example: if a target uses a
48 when adding support for a new build target.
62 Architecture (ISA) and related compiler configuration to create a binary for the
67 build, such as the target memory region for the binary. If a vendor,
69 should be separated by a hyphen and not an underscore.
71 For example, if we assume that a fictional company named Aperture developed its
72 own CHRE framework implementation, targeting a CPU family called Potato, and a
73 collection of platform software called GladOS/Cake, then a suitable build target
76 The build target may optionally have `_debug` appended, which is a common suffix
79 ### Creating a New Build Target
120 for a particular chipset, the same chipset can appear in multiple device
122 feature support, etc. Additionally, a device/chip vendor may wish to provide
140 At the end of a successful build, the following are generated in the `out`
143 * `<build_target>/libchre.so` and `libchre.a`: the resulting CHRE framework
144 binary, built as a dynamic/static library