Add instructions for using Alire to get binaries #40
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It literally took me hours to get
gnattest
installed, from the point of reading the project's README to where I finally had a set of instructions that actually got the binaries on my PATH, so I thought I would save the next person the trouble.The README says to first install libadalang, but libadalang itself recommends to use the Alire crate. Unfortunately, it does not tell us how to do this, which is where many would drop off. If one ventures into the Alire docs and figure out the right incantations, one might end up with
alr build
, but it is very unclear where to go from here, asalr install
will not make libadalong available for gprbuild or anything used in libadalong-tools ... Actually, after runningalr -v
it does not seem to do anything for libraries? At least nothing is added under ~/.alire.At this point, I figured that there might be a crate for such a common set of tools to avoid all of this trouble, and lo and behold, there was ... not sure why this was missing from the README, though, as it is what most people are after.