-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
[spatial-hash] add new port #42197
[spatial-hash] add new port #42197
Conversation
Note: I will be converting your PR to draft status. When you respond, please revert to "ready for review". |
The usage has been tested successfully on |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
-find_dependency(Eigen3 REQUIRED) | ||
-find_package(PkgConfig REQUIRED) | ||
-pkg_check_modules(glog REQUIRED IMPORTED_TARGET libglog) | ||
- | ||
+find_package(Eigen3 REQUIRED) |
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.
find_dependency was correct before
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 fixed what I could but I'm still interested as to your thoughts on the static-depends-on-DLLs situation. Please feel free to reply and un-draft.
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@FrankXie05 @BillyONeal |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Sorry, been a hectic couple of days. Power has been out for me since Tuesday night |
There is no problem, but there seems to be a problem with azure bot. |
yuppi :) done :) . |
Is there anything I should do? |
Thanks for confirming that the DLL edge cases work out! |
Changes comply with the maintainer guide.
The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all
find_package
calls are REQUIRED, are satisfied byvcpkg.json
's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx.The versioning scheme in
vcpkg.json
matches what upstream says.The license declaration in
vcpkg.json
matches what upstream says.The installed as the "copyright" file matches what upstream says.
The source code of the component installed comes from an authoritative source.
The generated "usage text" is accurate. See adding-usage for context.
Only one version is in the new port's versions file.
Only one version is added to each modified port's versions file.
I'm not sure I understand this question. So I don't know what the answer should be.