Skip to content
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

[Halide] update to 10.0.0 #13580

Closed
alexreinking opened this issue Sep 17, 2020 · 1 comment · Fixed by #13860
Closed

[Halide] update to 10.0.0 #13580

alexreinking opened this issue Sep 17, 2020 · 1 comment · Fixed by #13860
Assignees
Labels
category:port-update The issue is with a library, which is requesting update new revision

Comments

@alexreinking
Copy link
Contributor

Library name: Halide

New version number: 10.0.0

I am happy to report that the Halide team has finally released a new major version, 10.0.0! It's a big update from the last stable release and comes with an all new CMake package config with important helpers.

Please let me know what I can do to help you update. We now use GNUInstallDirs, so the existing fix-install-path.patch should no longer be necessary; just set CMAKE_INSTALL_DATADIR=share/Halide. Regarding patches generally, we would much prefer to upstream any changes that make packaging easier, rather than have you maintain separate patches.

References

All of our CMake packaging code is in: https://github.com/halide/Halide/blob/release/10.x/packaging/CMakeLists.txt

The CI scripts we use to package on Unix / Windows are here:

https://github.com/halide/Halide/blob/release/10.x/tools/package-unix.sh
https://github.com/halide/Halide/blob/release/10.x/tools/package-windows.bat

See also #11761

@JackBoosY JackBoosY added the category:port-update The issue is with a library, which is requesting update new revision label Sep 17, 2020
@alexreinking alexreinking changed the title Halide update to 10.0.0 [Halide] update to 10.0.0 Sep 17, 2020
@alexreinking
Copy link
Contributor Author

alexreinking commented Oct 2, 2020

Just checking in on this again... I've never written a vcpkg port file, but I'm very happy to pitch in any way I can here. Looks like someone has an issue with the old port right now, anyway. See #13823

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-update The issue is with a library, which is requesting update new revision
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants