Closed mgrojo closed 2 years ago
You cannot build AWA with Alire that way. I have to publish all the crates and manage the dependencies. It is a very long and painful process.
The alire.toml
file is using ADO 2.3.0 but the latest sources are using some additional developments which are not yet released. So, when you run alr build
it gets some dependencies that applied to AWA 2.4.0 but they are not correct for the next AWA version.
If you checkout the sources yourself, then, you should run the build steps that I described in AWA documentation. You also have to take care of other dependencies (compiler, XML Ada, AWS, libsqlite, libmariadb, libpq, ...) yourself before running the configure.
./configure
make
Ok. Thank you. I thought I might have discovered some bug worth of reporting, but it's already known, I see. I then checked-out tag 2.4.0, and it built cleanly, also using alr build
.
So the problem lies in inconsistencies between the versions being in the alire-index and the source code maintained in this repository? Are you aware of Alire pins. That would help to keep the Alire build always working between releases.
What I did:
On commit: dbbc6c69d43d056f9955759706b61a77a22868f5
Compilation errors: