Learning Objectives
#

After completing this section, you will be able to:

Create a VxWorks Source Build (VSB)
Create a VxWorks Image Project (VIP)
Understand the different configuration options for both VSB and VIP

The foundation of every VxWorks project lies in the source build (VSB) and the image project (VIP).

The VSB and VIP offer a wide range of customization options, enabling developers to tailor VxWorks to any project requirements.

VSB Configuration Options
#

The VSB project facility provides a rich set of configuration options to fine-tune the operating system build. Some of the most commonly used include:

BSP-specific optimizations – such as hardware floating-point support.
System Viewer instrumentation – for performance and debugging analysis.
Real-time processes (RTPs) – support user applications running in protected memory.
Object management – manage kernel objects like tasks, semaphores, and message queues.
Symmetric multiprocessing (SMP) – leverage multi-core processors efficiently.
Debug mode – add debugging symbols for development.
Advanced options – further low-level customization.

Parallel Builds
#

The parallel build feature uses Make to spawn additional threads and execute compiler or build rules simultaneously.

This speeds up build time by utilizing both CPU and RAM.
It works closely with the SMP scheduler.
Can be disabled in the build console if system resources are limited.

VIP Standard Profile Options
#

When creating a VxWorks Image Project (VIP), you must select a configuration profile. These profiles determine which kernel libraries are included or excluded, giving you a fast starting point:

`PROFILE_BOOTAPP`
#

Adds RAM-based bootloader functionality to a standard VxWorks image.

`PROFILE_BOOTROM`
#

Adds ROM-based bootloader functionality to a standard VxWorks image.

`PROFILE_DEVELOPMENT`
#

Includes development and debugging components, ideal for active software development.

`PROFILE_HARDENED`
#

Configures a security-hardened kernel image, strengthening the system against vulnerabilities.

`PROFILE_MINIMAL`
#

Strips down the configuration to produce the smallest possible kernel image.

The term STANDALONE in VxWorks can refer to a profile, library, or project type. It simply means the system is self-contained and does not require a network connection to run.

VSB vs VIP: Key Differences
#

Feature	VSB (VxWorks Source Build)	VIP (VxWorks Image Project)
Purpose	Defines and builds the kernel, middleware, and libraries	Creates a bootable OS image from a VSB configuration
Scope	System-level: OS features, compilers, layers, BSPs	Project-level: application-ready kernel image
Customization	Extensive options: SMP, RTPs, debug mode, etc.	Profile-based: bootloader, development, minimal, etc.
Output	Source tree and libraries	Bootable image (e.g., ROM, RAM, standalone)
Who Uses It	OS developers, BSP developers	Application developers, system integrators
Typical Workflow	Configure → Build → Export libraries	Select profile → Build → Deploy image