-
Notifications
You must be signed in to change notification settings - Fork 27
Log build steps in the outcome file #129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
gilles-peskine-arm
wants to merge
6
commits into
Mbed-TLS:main
Choose a base branch
from
gilles-peskine-arm:outcome-log-make-3.6-framework
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+112
−2
Open
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
0560e56
Record build steps in the outcome file
gilles-peskine-arm ef8d12d
Ignore weirdness from cmake
gilles-peskine-arm a5a28ed
Write an outcome file line for every component
gilles-peskine-arm 4ce986e
Don't log `make -q` calls in the outcome file
gilles-peskine-arm a11f2eb
Outcome lines from make: indicate when using a different makefile
gilles-peskine-arm e71d3b3
Less misleading outcome file line for every component
gilles-peskine-arm File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are both "--directory=somedir" and "--directory somedir" required?
For example would passing "--directory" and nothing else assert
skip=1
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With
--directory=...
, we want to remember the option and move on to the next argument which is another option or a non-option argument. With--directory
, we want to skip the next argument, which is the argument of the--directory
option.make --directory
is invalid. I don't know what the code here does in this case, but I don't think this wrapper needs to care about invalid usage ofmake
.