foxBMS 2 Logo
1.5.1

General Information

  • 1. Releases
  • 2. Changelog
  • 3. Motivation
  • 4. Safety
  • 5. License
  • 6. Team

Introduction

  • 1. Abbreviations and Definitions
  • 2. Naming Conventions
  • 3. The foxBMS 2 Platform
  • 4. Use Case

Getting Started

  • 1. Getting Started with foxBMS 2
  • 2. Repository Structure
  • 3. Software Installation
  • 4. Creating a Workspace
  • 5. First Steps on Hardware

Software Documentation

  • 1. Configuration
  • 2. Building the Application
  • 3. Software Structure Overview
  • 4. Software Modules
  • 5. Unit Tests
  • 6. Build Process
  • 7. Build Environment
  • 8. How-to
    • 8.1.1. How to Use the CAN Module
    • 8.1.2. How to Use the Diagnosis Module
    • 8.1.3. How to Use the Database Module
    • 8.1.4. How to Use the FTASK Module
    • 8.1.5. How to Use assertions
    • 8.2.1. How to Implement an Analog Front-End Driver
    • 8.2.2. How to Implement a New Temperature Sensor Driver
    • 8.2.3. How to Write State Machines
    • 8.2.4. How to Use Generated Sources from HALCoGen
    • 8.2.5. How to use unit tests
    • 8.2.6. Guidelines for the Unit Test Skeleton
    • 8.2.7. Result
    • 8.2.8. How to exclude files from unit tests
    • 8.2.9. Using ceedling directly
    • 8.2.10. Changing and Extending the Build Environment
    • 8.2.11. Existing Environments
    • 8.2.12. Further Reading
    • 8.2.13. How to Build A Library and Link it in a foxBMS 2 Project
  • 9. Linker Script
  • 10. Software Architecture
  • 11. API

Hardware Documentation

  • 1. Hardware
  • 2. Design Resources
  • 3. Connectors
  • 4. Master Overview
  • 5. Slaves Overview
  • 6. Interfaces Overview

System Documentation

  • 1. System Introduction
  • 2. System Voltage And Current Monitoring

Tools Documentation

  • 1. DBC File
  • 2. foxBMS 2 GUI
  • 3. Waf Tools
  • 4. Debugging the Application
  • 5. HALCoGen tool documentation
  • 6. Axivion Bauhaus Suite

Developer Manual

  • 1. Preface
  • 2. Style Guide
  • 3. Software Developer Manual
  • 4. Hardware Developer Manual
  • 5. Public Release Process

Miscellaneous Information

  • 1. Acknowledgements
  • 2. Indices and Tables
  • 3. Bibliography
foxBMS 2
  • »
  • 8. How-to »
  • 8.2.13. How to Build A Library and Link it in a foxBMS 2 Project
  • View page source

8.2.13. How to Build A Library and Link it in a foxBMS 2 Project

Sometimes source code can not be shared between parties. For these cases the foxBMS 2 project provides a mechanism to ship a minimal development project to the other party. This allows the partner to build a static library. This library and the accompanying headers can then be shared with the partner and be included in the application.

The following example describes the workflow. In this scenario partner A develops on foxBMS 2 while Part B should only provide a library to A.

  • A bootstraps a minimal development project. This minimal project is named library-project.tar.bz2.

    Listing 8.48 Bootstrapping the minimal library project
    C:\Users\Partner_A\Documents\foxbms-2>waf.bat bootstrap-library-project
    
  • A shares the archive library-project.tar.bz2 with B.

  • B installs a Code Composer Studio as described in Installing Code Composer Studio.

  • B installs a Python environment as described in Installing Miniconda and Configuration.

  • B builds a library by adding sources etc. to the minimal project as needed and builds the library.

    Listing 8.49 Building the Library
    C:\Users\Partner_B\Documents\foxbms-2>waf.bat build
    
  • B shares the library and accompanying headers with A.

  • A saves the library and accompanying headers and adds the path to the library to the search path, the library name the list of used libraries and the path to the headers to the include path (in cc-options.yaml).

Fork me on GitHub
Previous Next

© Copyright 2010 - 2023, Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V. All rights reserved. See license section for further information.

Built with Sphinx using a theme provided by Read the Docs.