Llvm20 #236
Merged
Llvm20 #236
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
* Also removed quick experiment that was accidentally committed [OOPS!]
* Includes some typo corrections in the markdown files
* Reworks the docfx.json project for greater readability
- That's a complicated beast with little in the way of good docs.
- What docs do exist are not consistent with either the officially published schema or, the actual use...
* Corrected typos in the `documentation.msbuildproj` file
* Removed reference to legacy ruleset from solution.
- no longer used (or even in tree)
* Bumped version XML to match current LLVM values
- While there isn't a guarantee of matching numbers, best effort is applied so that as long as it is possible/reasonable it is done.
- In other words, break this pattern only if necessary.
- Resynched so that common build is not the same as the LibLLVM repo
* Refined derivation checks to handle interfaces as the "base" uniquely * updated message on docs build project for clarity and easier readability in build logs.
- Addition of analyzer triggers a warning, which is treated as an error by the build.
- Added more logging to figure out why it is complaining that the analyzer isn't built... - Updated spelling dictionary
- For reasons unknown, SOME of the diagnostic output is ignored...
- Shifts to directly calling the build-docs script and FullInit from there.
- Hopefully this can shed light on why it thinks it isn't an automated build...
- My head hurts..., what a total PITA...
- PS has screwball behavior for script modules and preference vars so most things in the module don't properly report...
- DOCFX has a problem where it detects analyzers even if the MSBUILD setting to disable them is provided.
- The former build had treated docfx warnings as errors and that failed the action.
- That's the big one that's causing the most pain so is removed in this commit.
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.
No description provided.