winbuild/README: document how to clean a build - #15291
Closed
jay wants to merge 1 commit into
Closed
Conversation
Member
Author
|
The prose error due to many warnings appears to be unrelated: |
- Add a new section explaining that a build can be cleaned by adding the keyword "clean" to the build command. - Add an example of using the "x64 Native Tools" prompt to the VS command prompt section. - Update the Legacy Windows section's lack-of-cipher support warning to say "Windows 8 and earlier" instead of "Windows XP and earlier." Ref: curl#15277 Closes #xxxx
jay
force-pushed
the
update_winbuild_README
branch
from
October 14, 2024 09:00
4064607 to
af2a006
Compare
Member
Trying to address some of them in #15293. |
vszakats
added a commit
that referenced
this pull request
Oct 15, 2024
Fix new issues found by `proselint`. Also: - silence this technical warning: ``` :0: DeprecationWarning: /home/runner/.proselintrc was found instead of a JSON file. Rename to /home/runner/.proselintrc.json. ``` - fix an input filename. `proselints` fails now if an input file is missing. Reported-by: Jay Satiro Bug: #15291 (comment) Closes #15293
bagder
approved these changes
Oct 16, 2024
pps83
pushed a commit
to pps83/curl
that referenced
this pull request
Apr 26, 2025
Fix new issues found by `proselint`. Also: - silence this technical warning: ``` :0: DeprecationWarning: /home/runner/.proselintrc was found instead of a JSON file. Rename to /home/runner/.proselintrc.json. ``` - fix an input filename. `proselints` fails now if an input file is missing. Reported-by: Jay Satiro Bug: curl#15291 (comment) Closes curl#15293
pps83
pushed a commit
to pps83/curl
that referenced
this pull request
Apr 26, 2025
- Add a new section explaining that a build can be cleaned by adding the keyword "clean" to the build command. - Add an example of using the "x64 Native Tools" prompt to the VS command prompt section. - Update the Legacy Windows section's lack-of-cipher support warning to say "Windows 8 and earlier" instead of "Windows XP and earlier". Ref: curl#15277 Closes curl#15291
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
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.
Add a new section explaining that a build can be cleaned by adding the keyword "clean" to the build command.
Add an example of using the "x64 Native Tools" prompt to the VS command prompt section.
Update the Legacy Windows section's lack-of-cipher support warning to say "Windows 8 and earlier" instead of "Windows XP and earlier."
Ref: #15277
Closes #xxxx