Introduction

Provides the unified logic framework for a package's installation procedure by the SDK, such as is the case for libraries, binaries and additional initial scripts. For most applications, no further action or customization should be required other than adding this file as an include on the package's Makefile file.

Public Parameters

The following is a list of parameters that may be set according to an application's specific requirements.

• CORRECT_LA: This variable holds all .la files that whose "wired paths" have to be corrected after using the --prefix option pointing to /usr/, due to having to use external libraries such as gstreamer. Check the Development and Integration guide for specific examples on the usage of this variable.

• CORRECT_PKGCONFIG: This variable holds all pkgconfig (.pc) files that whose "wired paths" have to be corrected after using the --prefix option pointing to /usr/, due to having to use external libraries such as gstreamer. Check the Development and Integration guide for specific examples on the usage of this variable.

• CORRECT_DBUS_SERVICE: This variable holds all DBUS services files that whose "wired paths" have to be corrected after using the --prefix option pointing to /usr/, due to having to use external libraries such as gstreamer. Check the Development and Integration guide for specific examples on the usage of this variable.

• CORRECT_LA_SED_EXPRESSION: Sed regular expression used to parse and detect .la file names.

• CORRECT_PKGCONFIG_SED_EXPRESSION: Sed regular expression used to parse and detect Pkg-Config files filenames.

• CORRECT_DBUS_SERVICE_SED_EXPRESSION: Sed regular expression used to parse and detect DBUS Services filenames.

• BINARIES: A list of binaries within the output of the build process that are intended to be placed on the target's final file system. This allows you to filter out non-essential content from the output of the build process that could be needed in the development file system (FSDEV variable) but not in the target's file system.

• LIBRARIES: A list of libraries within the output of the build process that are intended to be placed on the target's final file system. This allows you to filter out non-essential content from the output of the build process that could be needed in the development file system (FSDEV variable) but not in the target's file system.

• LIBRARIES_OPTIONAL: A list of optional libraries within the output of the build process that are intended to be placed on the target's final file system. This allows you to filter out non-essential content from the output of the build process that could be needed in the development file system (FSDEV variable) but not in the target's file system.

• DIRECTORIES: A list of optional libraries within the output of the build process that are intended to be placed on the target's final file system. This allows you to filter out non-essential content from the output of the build process that could be needed in the development file system (FSDEV variable) but not in the target's file system.

• OTHERS: A list of other files (found within the directory assigned to the "OTHER" variable) within the output of the build process that are intended to be placed on the target's final file system. This allows you to filter out non-essential content from the output of the build process that could be needed in the development file system (FSDEV variable) but not in the target's file system.

• LINKS: A list of links within the output of the build process that are intended to be placed on the target's final file system. This allows you to filter out non-essential content from the output of the build process that could be needed in the development file system (FSDEV variable) but not in the target's file system.

• EXTRA_FILES: A list of extra files (found within the directory assigned to the "EXTRA" variable) within the output of the build process that are intended to be placed on the target's final file system. This allows you to filter out non-essential content from the output of the build process that could be needed in the development file system (FSDEV variable) but not in the target's file system.

• INIT_SCRIPT: Specifies the location of the initialization script (if any) that must go into the target platform, alongside whatever it is that should be stored in the target's filesystem after installation.

• INIT_SCRIPT_LEVEL: Specifies the level at which the aformentioned initialization script must be run (therefor, only neccesary if an init. script exists at all).

• VALA_BINDINGS: A list of the Vala bindings within the output of the build process that are intended to be placed on the directory determined by the VALADIR variable. This allows you to filter out non-essential content from the output of the build process that could be needed in the development file system (FSDEV variable) but not in the target's file system.

• VALADIR: Directory in which the Vala bindings specified through the aforementioned VALA_BINDINGS variable will be moved.

• RRSDK_PREPATCH_TARGETS: In case that any rule must be added so that it executes before the patch rule is executed, such rule must be stored into this variable. The targets must create real files otherwise the build system will attempt to patch already patched files, thus causing quilt to fail.

• RRSDK_POSTUNPATCH_TARGETS: rule to allow undoing anything done by the RRSDK_PREPATCH_TARGETS