snippets

The snippets folder contains portions of buildfiles that mkqnximage uses to create partitions for the SD card image generated by the project build. The mkqnximage utility combines these files with boilerplate snippets to assemble full buildfiles (.build), that are required to generate partition files (.part) for the image generation process.

The CTI contains the following snippets:

SnippetAbout
data_files.customAdds files to the /data partition.
data_files.custom.camera_demoIncludes entries for the files required by the camera.
data_files.homeIncludes entries for the user home directories and some local user configuration files.

If you integrate a new utility that can benefit from a default local configuration file, you can add the local configuration entries in this snippet for each user account that requires them.

If you add a new user account, you need to add extra entries here to create the new user folder and extra configuration files.

Refer to the entries for qnxuser as an example of what entries to add for another user.

ifs_env.~10.customContains entries for setting up the basic runtime environment of the IFS.
post_start.~15.networkingContains extra networking commands to add to the startup script, /system/etc/startup/post_startup.sh.
post_start.~40.window_managerContains extra commands that start the window manager. Add to the /system/etc/startup/post_startup.sh startup script.
post_start.~97.multimediaContains extra commands that start the multimedia renderer. Add to the /system/etc/startup/post_startup.sh startup script. Other utilities (such as mmrplay) use the multimedia renderer for media playback.
post_start.~98.install_pipContains extra commands to add to the /system/etc/startup/post_startup.sh startup script. These extra commands check if pip is installed and install pip if it isn't.
post_start.~99.finalContains extra commands to add to the startup script found at /system/etc/startup/post_startup.sh. These commands are meant to be the last thing executed at the end of the startup script.
profile.customContains extra environment variables or entries to add into /system/etc/profile to add global environment variables to each user's environment when they start a new shell.

If you integrate a new open-source service that needs defined environment variables to operate, you'd need to make changes to this snippet.

system_files.custom.commonMerged into the system partition buildfile. Serves as a general location where you can add extra entries for files to be integrated into the system partition. Extra snippets, where subsets of entries are added following a specific theme or service, are covered below.

For extra integrations, you have a choice to update this snippet with extra system entries or create a subset snippet to do so.

system_files.custom.camera_demoMerged into the system buildfile. Contains entries related to sensor framework and camera libraries, and sample apps, mainly to make it easier to locate and differentiate from other integrations that may be modified less often.
system_files.custom.io-sndMerged into the system buildfile. Contains entries related to the io-snd framework, ALSA support, and related sample apps.
system_files.custom.SDLContains entries to integrate the SDL libraries currently integrated into this project.
system_files.custom.window_managersContains entries relating to the two window managers integrated into the project, as well as their assets and configuration files.
system_files.custom.window_managers_demolauncher_configContains entries related to the configuration of the demolauncher window manager. This snipper is broken out separately from the main system_files.custom.window_managers file to allow variant specific demolauncher configuration.
system_files.custom.window_managers_screenwmContains entries related to the optional screenwm window manager. This snippet is broken out separately from the main system_files.custom.window_managers file to allow variant specific screenwm behavior.
wifi.custom (Optional)This snippet contains a network block that is injected into the wpa_supplicant.conf file for Wi-Fi settings.

Refer to the "Wi-Fi" section of the QSTI chapter for more details on how to populate the file.

This method of setting Wi-Fi settings isn't recommended unless your image is for devices that are operating in a fixed environment (e.g., school, corporate lab, or guest network), as opposed to being shared to the QNX developer community.

Page updated: