Follow these steps to build the drivers:

1. Open a terminal and navigate to the MCAL source directory and build/ folder.
2. Use the appropriate build target to build the required library or executable binary (.xer5f)/ user application (.appimage).
   1. The build command syntax for Sitara MCU is:make [-s] <build_target> [PLATFORM=<soc_name>] [PROFILE=<release/debug>] ...

      In this command, options shown inside square brackets [ ] are optional and not required to be provided for a build unless intended to be changed from the set default.

      1. The -s flag is used to suppress additional make command logs to simplify the make output.
      2. PLATFORM is the target device series to build for. As an example, for the AM273x Sitara™ MCU family, the PLATFORM option can take values from am273x and am2732s
      3. PROFILE sets the build optimization level. Debug build is an unoptimized build that can easily be stepped through and followed along during execution, release build is built for efficient optimizations around the timing and memory span of the compiled source.
   2. The build command syntax for Sitara MPU, Jacinto devices is:make [-s] <build_target> [BOARD=<device_evm_name>] [SOC=<soc_name>] [SDK_INSTALL_PATH=<sdk_install_path>] [PROFILE=<release/debug>] ...

      In this command, options shown inside square brackets [ ] are optional and not required to be provided for a build unless intended to be changed from the set default under the build/Rules.make file.

      1. The -s flag is used to suppress additional make command logs to simplify the make output.
      2. BOARD and SOC are the target device series. As an example, for AM6x Sitara™ MPU family, the <soc_name> option can take values from am62x, am62ax, or am62px. For the Jacinto family the <soc_name> option can take values from a valid j7xxx.
      3. SDK_INSTALL_PATH is the installation path of the corresponding MCU+ SDK RTOS for the SOC family that is present at the installation location.
      4. PROFILE gives the build optimization level. debug build is an unoptimized build that can easily be stepped through and followed along during execution. release build is built for efficient optimizations around the timing and memory span of the compiled source.
3. Once the build finishes, find the generated files under the binary/ directory within the package, right above the build folder. Driver libraries are in .aer5f format and an example application is the .xer5f executable and flashable .appimage file.

For a build to be performed, the build target name is the only required item in the make build command. Other available values can be updated by passing the property NAME = <value>; otherwise, the default value for a respective package gets used in build. The build commands only work with the standalone MCAL package. The commands are not the same if the MCAL is a part of an entire AUTOSAR stack delivered by any one vendor as each vendor uses unique compilation settings.

Build-related details and additional information is found under the user guide content.