Small changes to Mac install instructions. #582
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added instructions for finding the X11 path, as well as clarifying what the directory should look like.
billetd
changed the title
Added instructions for users with ARM64 architecture Macs. This is required so the shared executable are compiled correctly.
|
Added some additional instructions for users on newer Macs, as they have a different CPU architecture (ARM64 on M1 Macs and newer, versus x86_64 for Intel based Macs). Rosetta, the Apple back-compatibility translation layer, is required in order to compile some shared executables (such as those for using AACGM, file reading) to work correctly. |
|
This looks good! Not sure why the mkdocs check is failing (not just for this PR) -- it works just fine when I build it locally. Merging now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added instructions for finding the X11 path, as well as clarifying what the directory should look like (i.e., not ending in the
includesub directory.Mentioned in issue #581