This repository was archived by the owner on Jul 15, 2023. It is now read-only.
Add options to cccheck to find source in a different location #462
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.
cccheck
currently reads the paths to source files out of the PDBs. This is required for some suppressions to work, e.g.RequiresAtCall
.What I need to be able to do for distributed testing is build in one path, e.g.
C:\Build\MyProject
, and then invokecccheck
from another computer entirely in a different path, e.g.C:\Testing\TestRun001\MyProject
.This pull request adds two command-line flags.
-sourcePaths
lists partial paths that the project was built from.-alternativeSourcePaths
lists alternative/substitute paths that can be used to replace a partial path from-sourcePaths
.For example, with these changes I can successfully test an assembly in the scenario above by running:
If you don't supply both
-sourcePaths
and-alternativeSourcePaths
, these changes have no other effect.This goes hand-in-hand with #459.