Building OS and Flash ImagesWorkflow of OS image development | Parent topic: Workflow of OS image development |
| ! $ ( " ) & ` : ; \ ' * ? [ ] # ~ = % < > { }
These characters cause problems later because the build tools don't like them.
In the same dialog, you can also override the project storage location and specify the working sets that you want the project to belong to.
When you're finished configuring these first settings, click Next.
Option | Description |
---|---|
Create default build file | Choose this option if you plan to write your own buildfile. You must then select your desired platform from the dropdown list. |
Import from a BSP project | Choose this option to import a buildfile from an existing BSP project. You must then select the project from the dropdown list. |
Copy an existing buildfile | Choose this option if you want to reuse or adapt an existing buildfile. You must click Browse… and choose the file from the selector. Refer to your BSP documentation for the proper .build file for your board. You can find buildfiles for all BSPs installed on your host by looking in $QNX_TARGET/processor/boot/build/. |
Name | Platform(s) | Description |
---|---|---|
apic | x86 | Creates a minimal buildfile with APIC initialization code (i.e., a startup-apic command) |
bios | x86 | Creates a detailed buildfile with BIOS initialization code (i.e., a startup-bios command), a startup script, and several libraries |
(no template) | x86, ARM (Little-endian), ARMv7 (Little-endian) | Creates a generic minimal buildfile, based on your selections in the Boot file and Startup dropdown lists |