Practical Guide to Bare Metal C++
  • Introduction
  • Audience
  • C++ Popularity
  • Benefits of C++
  • Contents of This Book
  • Contribution
  • Know Your Compiler Output
    • Test Applications
    • Get Simple Application Compiled
    • Dynamic Memory Allocation
    • Exceptions
    • RTTI
    • Removing Standard Library and C++ Runtime
    • Static Objects
    • Abstract Classes
    • Templates
    • Tag Dispatching
  • Basic Needs
    • Assertion
    • Callback
    • Data Serialisation
    • Static (Fixed Size) Queue
  • Basic Concepts
    • Event Loop
    • Device-Driver-Component
  • Peripherals
    • Timer
    • UART
    • GPIO
    • I2C
    • SPI
    • Other
Powered by GitBook
On this page

Was this helpful?

  1. Know Your Compiler Output

Test Applications

PreviousKnow Your Compiler OutputNextGet Simple Application Compiled

Last updated 5 years ago

Was this helpful?

The project contains several simple test application, which are intended to be used for binary code analysis only and not to be executed on the target platform. This applications reside in directory. In order to properly analyse the code that compiler produces for production environment, let's compile all the applications in Release mode:

> git clone https://github.com/arobenko/embxx_on_rpi.git
> mkdir -p <build_dir_somewhere>
> cd <build_dir_somewhere>
> cmake -DCMAKE_BUILD_TYPE=Release <path/to/embxx_on_rpi>
> VERBOSE=1 make

The listing file of every application will be <build_dir_somewhere>/src/test_cpp/<app_name>/kernel.list.

embxx_on_rpi
src/test_cpp