OpenAA: Adaptive AUTOSAR C++17 Project

This is a modular and scalable open-source Adaptive AUTOSAR demo using C++17. The project utilizes CMake for build configuration, facilitating easy integration, testing, and future expansions.

Key Features

• Modular Architecture: Easily add or remove components as needed.
• Scalable Design: Suitable for small-scale applications and large automotive systems.
• Comprehensive Testing: Includes tests to ensure reliability and correctness.
• Cross-Platform Support: Build and run on both Linux and QNX platforms with various architectures.

Repository Structure

.
├── CMake
│   ├── CMakeConfig
│   │   ├── gcc11_linux_aarch64_debug.cmake
│   │   ├── gcc11_linux_aarch64_release.cmake
│   │   ├── gcc11_linux_x86_64_debug.cmake
│   │   ├── gcc11_linux_x86_64_release.cmake
│   │   ├── qcc12_qnx800_aarch64_debug.cmake
│   │   ├── qcc12_qnx800_aarch64_release.cmake
│   │   ├── qcc12_qnx800_x86_64_debug.cmake
│   │   └── qcc12_qnx800_x86_64_release.cmake
│   └── Toolchain
│       ├── CMakeLogging
│       │   └── tool_chain_log_config.cmake
│       ├── gcc11_linux_aarch64_debug.cmake
│       ├── gcc11_linux_aarch64_release.cmake
│       ├── gcc11_linux_x86_64_debug.cmake
│       ├── gcc11_linux_x86_64_release.cmake
│       ├── qcc12_qnx800_aarch64_debug.cmake
│       ├── qcc12_qnx800_aarch64_release.cmake
│       ├── qcc12_qnx800_x86_64_debug.cmake
│       └── qcc12_qnx800_x86_64_release.cmake
├── CMakeLists.txt
├── CMakePresets.json
├── LICENSE
├── README.md
├── build.sh
├── components
│   ├── open-aa-platform-os-abstraction-libs
│   │   ├── CMakeLists.txt
│   │   ├── include
│   │   │   └── ara
│   │   │       └── os
│   │   │           ├── interface
│   │   │           │   └── process
│   │   │           │       ├── process_factory.h
│   │   │           │       └── process_interaction.h
│   │   │           ├── linux
│   │   │           │   └── process
│   │   │           │       └── process.h
│   │   │           └── qnx
│   │   │               └── process
│   │   │                   └── process.h
│   │   └── src
│   │       ├── CMakeLists.txt
│   │       └── ara
│   │           └── os
│   │               ├── interface
│   │               │   └── process
│   │               │       ├── CMakeLists.txt
│   │               │       └── process_factory.cpp
│   │               ├── linux
│   │               │   └── process
│   │               │       ├── CMakeLists.txt
│   │               │       └── process.cpp
│   │               └── qnx
│   │                   └── process
│   │                       ├── CMakeLists.txt
│   │                       └── process.cpp
│   └── open-aa-std-adaptive-autosar-libs
│       ├── CMakeLists.txt
│       └── include
│           └── ara
│               └── core
│                   ├── array.h
│                   └── internal
│                       └── location_utils.h
└── tests
    └── core_platform
        ├── CMakeLists.txt
        └── ara_core_array.cpp

31 directories, 39 files

Prerequisites

Before building the project, ensure that your system meets the following requirements:

• Operating System: Linux (tested on Ubuntu 22.04)
• C++ Compiler:
• GCC: Version 11.4.0 or later
• QNX QCC: Version 12 (for QNX builds)
• CMake: Version 3.27 or later
• Bash: Version 4.0 or later
• GNU Make: For building targets
• CMake Linting (Optional): cmakelint for linting CMake scripts

Installing Dependencies on Ubuntu

sudo apt update
sudo apt install -y build-essential cmake gcc-11 g++-11

Installing QNX SDP (for QNX Builds)

To build for QNX platforms, you need to install the QNX Software Development Platform (SDP). Please refer to QNX's official documentation for installation instructions.

Building the Project

The project is built via the build.sh script. This script supports multiple configurations, different toolchains, architectures, and exception safety modes.

Usage

./build.sh [OPTIONS]

Options

• -h or --help: Show help message and exit.
• -c or --clean: Perform a clean build by removing build and install directories.
• -t or --build-type TYPE: Specify the build type (Debug or Release). Default is Release.
• -b or --build-target TARGET: Specify the build target. Supported options:
  • gcc11_linux_x86_64
  • gcc11_linux_aarch64
  • qcc12_qnx800_aarch64
  • qcc12_qnx800_x86_64
• -s or --sdp-path PATH: Specify the path to qnxsdp-env.sh for QNX builds.
• -j or --jobs N: Specify the number of parallel jobs for the build. Defaults to number of CPU cores.
• -e or --exception-safety MODE: New: Specify exception safety mode:
  • conditional (default): only enable ARA_CORE_ARRAY_ENABLE_CONDITIONAL_EXCEPTIONS
  • safe: do not define that macro (i.e., “safe” mode)

Example Commands

Clean and Build for GCC 11 Linux x86_64 (Release)

./build.sh --clean -b gcc11_linux_x86_64 -t Release -j 8

Build for QNX aarch64le (Debug) with safe exception mode

./build.sh -b qcc12_qnx800_aarch64 -t Debug -s /path/to/qnxsdp-env.sh -e safe -j 4

Build for GCC 11 Linux aarch64le (Release) with conditional exceptions

./build.sh --clean -b gcc11_linux_aarch64 -t Release -e conditional

Clean and Build for QNX x86_64 (Release)

./build.sh --clean -b qcc12_qnx800_x86_64 -t Release -s /path/to/qnxsdp-env.sh -j 4

Build Targets

The project supports the following build targets:

Build Target	Compiler	Platform	Architecture	Build Type
gcc11_linux_x86_64	GCC 11	Linux	x86_64	Release/Debug
gcc11_linux_aarch64	GCC 11	Linux	aarch64le	Release/Debug
qcc12_qnx800_aarch64	QCC 12	QNX	aarch64le	Release/Debug
qcc12_qnx800_x86_64	QCC 12	QNX	x86_64	Release/Debug

Note: Append Debug or Release internally based on --build-type, set by the script.

Testing the Project

The tests directory contains test apps for the project. After building, tests can be executed as follows:

cd install/<build-target>/
./platform_core_test/bin/ara_core_array_test [OPTION]

Advanced Configuration

Adding a New Build Target

1. Create a New CMake Configuration File:

   • Navigate to CMake/CMakeConfig/ and create a new .cmake file based on existing configurations.

2. Define the Build Target in the Build Script:

   • Update the build.sh script to recognize the new build target and map it to the appropriate configuration file.

3. Update CMakePresets.json:

   • Add a new preset corresponding to the new build target for seamless integration with CMake.

Integrating Additional Components

1. Add a New Component Directory:

   • Create a new directory under components/ for your component.

2. Define CMakeLists.txt for the Component:

   • Ensure that the component's CMakeLists.txt properly sets up include directories, dependencies, and installation les.

3. Include the Component in the Root CMakeLists.txt:

   • Add add_subdirectory(components/your-component) to include it in the build process.

Troubleshooting

Common Issues

1. CMake Not Found:

   • Error:

     cmake: command not found
     

   • Solution: Ensure that CMake is installed and added to your PATH.

     sudo apt install -y cmake

2. QNX Environment Variables Not Set:

   • Error:

     Error: QNX_HOST and QNX_TARGET environment variables must be set.
     

   • Solution: Ensure correct SDP path or environment is sourced via -s /path/to/qnxsdp-env.sh.

3. Toolchain File Not Found:

   • Error:

     Error: Toolchain file not found: CMake/CMakeConfig/gcc11_pikeos5_armv8hf.cmake
     

   • Solution: Verify that the toolchain file exists in the specified directory and that the build target is correctly specified.

4. Compilation Errors:

   • Cause: Possible mismatches between compiler versions or missing dependencies.
   • Solution: Ensure that the correct compiler is being used and all dependencies are installed.

Getting Help

If you encounter issues not covered in this section, feel free to open an issue on the GitHub repository.

Contributing

Contributions are welcome! Please follow these steps to contribute:

1. Fork the Repository: Create your own fork of the project.
2. Create a Feature Branch: Develop your feature or bug fix in a separate branch.

   git checkout -b feature/my-new-feature

3. Commit Your Changes: Make your changes and commit them with descriptive messages.

   git commit -m "Add new feature XYZ"

4. Push to Your Fork: Push your changes to your forked repository.

   git push origin feature/my-new-feature

5. Submit a Pull Request: Open a pull request against the master_integration branch of the main repository.

License

This project is licensed under the MIT License. See the LICENSE file for details.