Installer build: pre-flight diagnostics + verbose ISCC#9
Merged
Conversation
ISCC's default error message ("The system cannot find the path
specified.") doesn't say which file failed, which made the Gitea
runner failure undebugable. Two changes:
1. Before invoking ISCC, log a one-line summary per source path the
.iss references: file count, longest path length, root. Also dump
HKLM\...\FileSystem\LongPathsEnabled so MAX_PATH issues are
immediately obvious.
2. Pass /Qp to ISCC so it prints each file as it processes; the line
right before the error tells us which source file ISCC choked on.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Adds source-path summary + LongPathsEnabled status + /Qp to ISCC so we can see which file the Gitea build is failing on.