Skip to content

Latest commit

 

History

History
55 lines (40 loc) · 1.74 KB

README.md

File metadata and controls

55 lines (40 loc) · 1.74 KB
Raw

GNAT-FSF-builds

Builds of the GNAT Ada compiler from FSF GCC releases

How to build

To start the builds you will need python3 and the e3-core package. This can be done in a virtual env, e.g.:

$ python3 -m venv my-virtual-env
$ source my-virtual-env/bin/activate
$ pip install e3-core==22.1.0

To build a spec, for example mpc, run the anod script:

$ ./anod build mpc -v --loglevel DEBUG

-v --loglevel DEBUG will produce many information log about the build.

For a cross compiler:

$ ./anod build gcc --target=avr-elf -v --loglevel DEBUG

On Windows

Only builds in the msys2 mingw64 environement are supported. You will need:

  • mingw-w64-x86_64-python-psutil package for e3-core installation to work.

  • The Unix and Windows PATH of the repo checkout must match: C:\dir1\dir2\GNAT-FSF-builds <-> \dir1\dir2\GNAT-FSF-builds. This can be done by "mounting" Windows directories in msys2, e.g.: mount C:/Users /Users.

Writing specs

Until the e3-core/anod documentation is available online, the best way to write a spec is to start from an existing one. A good starting point would be gnatcoll.anod.

  • First, change the version, tarball and, source_pkg_build url
  • Modify the list of build_deps, you probably need at least gcc.
  • Change the configure/make options

Publishing to the Alire index

A little script is available to speedup the process of publising GNAT FSF package to the Alire index.

Edit the PKG_VERSION and CRATE_VERSION constant and then run the script to generate all the GNAT manifests. The script also checks the correctness of sha256 hashes.