c10a6bada0
There are two color formats in HAL.Bitmap, the Bitmap_Color (with Alpha, Red, Green, Blue components) and the "native" raw value of the pixel. In the current interface users select a color for each operations (Fill, Draw_Line, Draw_Circle, etc.) which means each operation has to be declared twice, one with a Bitmap_Color and one with native pixel value. Inspired by the Cairo graphics library, this patch add a Set_Source primitive which allows to specify the color that will be use. Each drawing operation then uses this color for rendering. This simplifies the interface since drawing operation only have to be declared once. It may also allow for more advanced sources in the future like gradients or textures.
Ada_Drivers_Library testsuite
Without nice emulator support, testing bare-board code is hard. The goal of this testsuite is to leverage the native support packages in this repository to test services and components that rely on native implementations for HAL interfaces.
How to run the testsuite
First, make sure you have a Python 3 interpreter available, and then run:
./run.py
The standard output report should be obvious to read. In order to restrict the set of executed tests, run instead:
./run.py foo bar
This will execute all tests that have either foo or bar in their name
If Valgrind is available, add a --valgrind switch to detect memory issues
such as invalid operations or leaks.
How to write testcases
Every subdirectory in tests/ that contains a tc.gpr file is a testcase.
Each testcase embeds one or more test drivers (i.e. Ada programs) that run test
code and write to their standard output to demonstrate that some feature is
correctly implemented. For each test driver X, the project file must build an
executable as bin/X and there must be a X.out file next to the
tc.gpr project file that states what the test driver output should be for
the test to pass.