-
Notifications
You must be signed in to change notification settings - Fork 18
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
Implement Use CMake Header File Sets #30
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
26367d7
include folder is not working
wusatosi 735a7e6
fixed include header
wusatosi fc85080
removed unnecessary directives
wusatosi e2a8352
update dockerfile to reflect cmake change
wusatosi 6edc629
switch to CMAKE_INSTALL_LIBDIR
wusatosi f4ff6ac
remove INSTALL directive
wusatosi 62f37d9
Revert "remove INSTALL directive"
wusatosi b9b56e0
update DESTINATION location
wusatosi 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 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 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.
Not a big deal, but is the
--verbose
flag worth adding for theall_verify_interface_header_sets
command? If we see a compiler error in a CI log, do we see enough detail to identify the relevant compilation commands?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.
Sure I can add the verbose flag. Logs are free.
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.
#6 tries to remove the Dockerfiles. Maybe we should decide if we'll do that or not, as it may influence current PR.
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.
I have not checked failure case but I don't think verbose provide any useful information, should we still add the verbose flag?
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.
I can work on this later too but can you help me produce a case where the
all_verify_interface_header_sets
fails? I can go check the log and see if verbose provide more information.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.
For instance, I would expect the following to work in a normally-formed CMake library but fail an
all_verify_interface_header_sets
check.I just want to make sure the person looking at a failure log can tell:
something.hpp
is being checked with a specific compile command$some_build_dir/something.hpp.cpp
probably)If we get that with
--verbose
off, I'm happy. We can land a shorter log and everyone wins.If we don't get it regardless of whether
--verbose
is on or off, let's make an upstream CMake issue. I wouldn't expect tweaking this would be tricky or expensive for them.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.
Since #6 is closed, no worries on this PR, right?
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.
We shouldn't need to worry about that.
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.
Without verbose Flag
With Verbose Flag
Verbose doesn't provide more useful information, and honestly the error log is pretty bad. The error fails because it cannot find the
verify_something.hpp.cpp
, even with verbose on nothing indicate the reason for failure to generate this file.Tested on
cmake version 3.26.3
.Can someone test this on newer
cmake
version? We should file an issue upstream if no more helpful error message is generated.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.
I tested on
cmake version 3.30.3
, same output, I will file a issue upstream, let's omit the verbose flag.version 3.30.3 with verbose log