Build services#

This section is for implementing production-oriented VAPI services, from service modeling to build/integration details.

Use it when you want to:

  • design service responsibilities correctly,

  • implement and structure services in C++,

  • integrate build/runtime aspects into your project.

Why this matters#

Service code scales only if responsibilities are clear and implementation decisions stay aligned with the VAPI model.

This section helps you:

  • avoid mixing application orchestration with service logic,

  • keep implementation, build setup and runtime behavior aligned,

  • move from prototype examples to maintainable service projects.

What this section helps you do#

Services

Core service concepts and implementation guidance for Vehicle Devices, Basic Services and Complex Services.

Components & Services
For developers

Practical developer-focused guidance for everyday VAPI implementation and integration work.

For Developers
CMake in the project

Build system structure and CMake integration for service-centric development workflows.

CMake in the project
Under the hood

Runtime internals and lower-level details useful when debugging service integration.

A view under the hood

Quick paths#

If you are defining service boundaries and responsibilities, start with Components & Services.

If you are implementing and wiring components in daily development, start with For Developers.

If your immediate blocker is project/build setup, start with CMake in the project.

Where this fits in the journey#

After learning the core concepts in Learn the concepts, this section is the primary path to real implementation work.

For simulation-heavy workflows and deeper troubleshooting references, continue with Advanced & reference.

All pages in this section#