docs: the ways to name a tool are whole build programs, each compiled - #44
Merged
Merged
Conversation
The chapter stated four spellings by assigning the same option four times in one `main`, which is an index, not an example -- no project writes that. Each way is now a complete `build.mcpp`: a program path with deps-vcpkg, a tree with deps-cmake, PATH with rules-spirv, a toolkit root with rules-cuda, a plain root with rules-qt, and the vendored-plus-environment program with deps-vcpkg. Every one of them was compiled as a real build program before being written down, which is also how the missing `import mcpp.plugins.tool;` was found earlier. The table in 3.6 stays what it is: an index of which option each member reads and what it looks for under a root.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Follow-up to #43, documentation only.
Chapter 3 of
docs/tool-sources.mdstated the four spellings by assigning the sameoption four times in one
main. That reads as an index rather than an example, andno project writes it that way.
Each way is now a complete
build.mcpp:deps-vcpkgdeps-cmake(whose layout search differs from vcpkg's)rules-spirvrules-cudarules-qt-- whose option has always been a directorydeps-vcpkgandrerun_if_env_changedEvery example was compiled as a real build program against 0.19.0 before being
written down. That is how the missing
import mcpp.plugins.tool;was found whenthis chapter was first written: a feature makes a module available, not visible.
The table in 3.6 is unchanged and stays what it is -- an index of which option each
member reads and what it looks for under a root.