* muntsos_aarch64 release 11.0.1 Tue Dec 2 01:22:11 PM PST 2025
Add a post-build script to the superordinate program project that will
optionally scp the executable file(s) from bin/ to the MuntsOS Embedded
Linux target computer indicated by the TARGETCOMPUTER environment variable,
which must contain a value of the following form:
root@snoopy:/usr/local/bin
* muntsos_raspberrypi1 release 11.0.1 Tue Dec 2 01:22:57 PM PST 2025
Add a post-build script to the superordinate program project that will
optionally scp the executable file(s) from bin/ to the MuntsOS Embedded
Linux target computer indicated by the TARGETCOMPUTER environment variable,
which must contain a value of the following form:
root@snoopy:/usr/local/bin
* Add coap_spark-0.10.0
CoAP-SPARK is a library implementing the Constrained Application Protocol (CoAP) in SPARK/Ada, with client and server sides.
* Add coap_client-0.10.0
This only update the `xmlada` or `aws` dependencies in the crate declaration so that
these two crates can be used with AWS 25 + XML 25 as well as AWS 25 + XML 24
The declarations:
aws = "^24.0"
xmlada = "^24.0"
are not enough to allow that and the pull request only change them to accept ^25.0 explicitly.
This is a proposal for another way to integrate the Ada Web Server as a crate.
The issue with the current approach is the Makefile-based environment used
by AWS and the fact that we have to completely build and then install AWS
to use it.
In this proposal, only the 'make setup' phase is done to let the AWS Makefile
do the important setup and prepare the required files in target directory.
That target directory is named by AWS by using `gcc -dumpmachine` which brings
other issues and to solve and fix things, that directory is moved to a fixed
directory `build` so that every target will use that fix value.
The installation and build is not made and instead we reference the two
important GNAT projects 'aws.gpr' (top-level) and `build/projects/aws_config.gpr`
which was generated by `make setup`. The build is then handled by Alire
since it knowns the AWS projects. The AWS GNAT projects rely on the following
important variables which are set through the makefiles and we can set
them for each target as follows:
TGT_DIR = "../build"
TARGET = "build"
It is a proposal in the hope it will solve the AWS crate integration issues....
* Ada Binding to the GNU Binutils library
The Ada-BFD library allows to:
* list and scan the ELF sections of an executable or object file,
* get the content of the ELF sections,
* get access to the symbol table,
* use the BFD disassembler
Requires some binutils-dev
* Fix build