Skip to content

Add instructions for using Alire to get binaries #40

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

fatso83
Copy link

@fatso83 fatso83 commented Mar 12, 2025

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, as alr install will not make libadalong available for gprbuild or anything used in libadalong-tools ... Actually, after running alr -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.

@CLAassistant
Copy link

CLAassistant commented Mar 12, 2025

CLA assistant check
All committers have signed the CLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants