-
Notifications
You must be signed in to change notification settings - Fork 7.2k
[ms-ifc-sdk] Update to 0.43.5 #48746
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
Conversation
edfe87a to
7a5bf18
Compare
ports/ms-ifc-sdk/portfile.cmake
Outdated
| CONFIG_PATH "${config_path}" | ||
| ) | ||
|
|
||
| # Update this when https://github.com/microsoft/ifc/pull/109 is merged |
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.
If I understand correctly we need that PR for this new feature to actually do anything. Could you minimize the patch a bit and add it here? Since it's just disabling a whole build system part I think we could add that without the usual 30 day waiting periods.
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.
The question was: What should happen to the newly added tool? Always copy it via vcpkg_copy_tools or always remove it? That's why I added it as an option, so that you can choose between the two. An alternative would be to add a patch so that it isn't built at all.
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.
It makes sense to be an option but the option needs to actually be an option; as implemented it seems like the option is not connected because the tool is always built.
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.
So remove the option and:
Option 1) Always remove the tool, as no one has missed it so far.
Option 2) Always install the tool
Which option do you prefer?
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.
If we built it we may as well always install it.
BillyONeal
left a comment
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.
Thanks!
BillyONeal
left a comment
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.
Thanks!
| file(REMOVE_RECURSE | ||
| "${CURRENT_PACKAGES_DIR}/bin/" | ||
| "${CURRENT_PACKAGES_DIR}/debug/bin/" | ||
| ) |
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.
What are these for?
BillyONeal
left a comment
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.
Oh I see it's always a static library, OK. Thanks!
./vcpkg x-add-version --alland committing the result.Note: The tool was added in microsoft/ifc#59 (0.43.2)