Add native tools on machine doc #9891
Merged
Conversation
This file contains hidden or 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
MattGal
previously approved these changes
Jul 6, 2022
| 2. Modify your `global.json`'s `native-tools` section to change the version of your tools to one of the following values: | ||
| - `latest` (e.g. `"cmake": "latest"`) – Grabs the latest version of the tool on the machine; this should be what you use in the majority of cases | ||
| - Major version (e.g. `"cmake": "3"`) – Grabs the latest minor & patch version of a particular major version on the machine; this is useful artifacts you want to pin to a specific major version | ||
| - Minor version (e.g. `"python": "3.10"`) – Grabs the latest patch version of a particular minor version on the machine; this is useful for artifacts you want to pin to a specific minor version (such as Python) |
Member
There was a problem hiding this comment.
Do we actually provide multiple pythons ? WHy?
Contributor
Author
There was a problem hiding this comment.
No, this was just an example of a minor version specification. Python's the only case I could think of for that lol, but hypothetically there are other cases where you'd want to pin a minor version.
| - Major version (e.g. `"cmake": "3"`) – Grabs the latest minor & patch version of a particular major version on the machine; this is useful artifacts you want to pin to a specific major version | ||
| - Minor version (e.g. `"python": "3.10"`) – Grabs the latest patch version of a particular minor version on the machine; this is useful for artifacts you want to pin to a specific minor version (such as Python) | ||
| 3. Adjust any usage of the artifacts on the machines in your scripts. The artifacts you specify in your `global.json` are promoted to the path, | ||
| so in general simply calling `cmake` will work. However, if you need the specific locations of tools, `InitializeNativeTools` will return those to |
Member
There was a problem hiding this comment.
Consider combining lines here, this may look odd on some column widths.
Contributor
Author
There was a problem hiding this comment.
I do separate lines so it's easy to pinpoint comments in a PR; it all looks the same when it's rendered in markdown
ChadNedzlek
reviewed
Jul 6, 2022
MattGal
approved these changes
Jul 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Doc I wrote on Friday but forgot to post as a PR for some reason. Realized I should have a doc explaining migration that I can link to in the email so that's what this is.