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.
[ML] Generate windows resource files using CMake functionality #2321
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
[ML] Generate windows resource files using CMake functionality #2321
Changes from all commits
4764513
757b24a
452f28c
161299c
65985c8
247322f
dd29063
f38b0a7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This is OK, but it does now mean that in addition to the resource file all our C++ code is getting compiled with this extra symbol defined. I'm sure it won't be a problem as none of our source will contain this string.
It might be nicer to substitute it only into the resource file using the
@ML_FILEFLAGS@
syntax. Don't bother about doing this in this PR, because we want to get the overall feature branch merged soon. But maybe you could have a look at tidying this up next week in a separate PR against the main branch.