-
Notifications
You must be signed in to change notification settings - Fork 461
fix(#5566): updated two docs to make build steps clearer #5568
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
base: master
Are you sure you want to change the base?
Conversation
Clarified that the `agave-install` command shown is ONLY for installing the `test` or `prod` versions, and expects to be building from a downloaded release source archive, but can be managed by switching to a tagged release.
Added section 3a, describing the dependency install steps to get this installed on a macOS machine. Also changed wording on the accompanying NOTE quote.
|
||
# Include the installed bins in your PATH | ||
$ export PATH=$PATH:$PWD/bin | ||
$ ./cargo build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cargo-install-all.sh
contains building so extra ./cargo build
shouldn't be applied
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sonicfromnewyoke I put that there mostly for clarity that from this point the developer can start running the ./cargo build
again as they make changes. But if I misunderstood the use case of a local cargo definition then I can remove it?
|
||
```bash | ||
$ # Install build dependencies | ||
$ brew install pkg-config libudev protobuf llvm coreutils |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wdyt about moving this line a lil bit higher, just after On Fedora:
paragraph?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah good point, that makes more sense and flows better
Problem
See 5566 for clearer description.
Basically there's a lack of clarity in some of the build instructions for macOS.
Summary of Changes
This adds some additional clarity on what dependencies are needed to build on macOS and how the
./docs/src/cli/install.md
are specifically for buildingtest
/prod
versions.Fixes #5566