Builds of the GNAT Ada compiler from FSF GCC releases
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
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
.
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
.
version
, tarball
and, source_pkg_build
urlbuild_deps
, you probably need at least gcc
.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.