Build and configure Flyology Runtime.

Use a supported toolchain.

Flyology is an Alire crate and requires Alire 2.1 or newer. The dependency range accepts GNAT 13 through 16. Runtime preparation supports only the host and release pairs listed below.

Add Flyology to an Alire application.

Flyology is published through a separate organization index. Keep the community index enabled for compiler and third-party dependencies. Add the Flyology index before the community index, then add the crate. Flyology might move to the community index later, but no decision has been made.

alr init --bin flyology_app
cd flyology_app
alr index --reset-community
alr index --add=git+https://github.com/flyology-ada/alire-index.git \
  --name=flyology --before=community
alr with flyology

Build with a version-matched runtime.

The first build runs Flyology's Alire post-fetch action. The action copies the active compiler's installed runtime sources into the dependency build output. It then applies the exact patch family, builds the RTS, and exports a GPR configuration. The application links to this prepared RTS instead of the stock tasking runtime.

alr build

The default is native. In this compatibility configuration, undesignated tasks use stock OS-thread execution. No event machinery starts until a lightweight task activates.

FLYOLOGY_LOOP_POOL_SIZE=4 alr run

Continue with Execution groups to change the automatic pool after startup.

Designate one ordinary Ada task.

Use GNAT Task_Info to select the execution model at task creation. Current GNAT emits an obsolete-feature warning for this mechanism. The warning is an artifact of the current design and GNAT's handling of it, not intended Flyology behavior. Flyology projects use -gnatwJ to suppress that warning class while retaining other warnings.

A future design might use another designation mechanism, including an Ada aspect, if GNAT makes one available. Flyology has not selected a replacement.

with Flyology;

package Worker is
   task Connection is
      pragma Task_Info (Flyology.Lightweight_Task);
   end Connection;
end Worker;

Use Flyology.Native_Task and Flyology.Lightweight_Task for explicit task designations. Both are values of Flyology.Execution_Model. Flyology.Project_Default requests the project default explicitly, which is useful on discriminated task types.

alr build

Continue with one focused chapter.

The core path follows the setup above. Each later step has a stable page that you can open or link directly.

Core chapters

Topic guides

Project tooling