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.

Sign up for GitHub

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

Jump to bottom

[openvdb]Upgrade version to 6.1.0 #6864

Merged
merged 2 commits into from
Jun 26, 2019
Merged

[openvdb]Upgrade version to 6.1.0 #6864

merged 2 commits into from
Jun 26, 2019

Conversation

JackBoosY
Copy link
Contributor

@JackBoosY JackBoosY commented Jun 12, 2019 •
edited
Loading

  • Upgrade to 6.1.0
  • Regenerate patches
  • Fix build errors.

Note:

  1. vdb_render does not currently support(#302).
  2. vdb_view does not support win32 currently(source/openvdb/cmd/CMakeLists.txt:194).

Related: #6618.

It really took me a few hours.

@JackBoosY JackBoosY added the info:internal This PR or Issue was filed by the vcpkg team. label Jun 12, 2019
@JackBoosY JackBoosY changed the title [openvdb]Upgrade version to 6.1.0, regenerate patches and fix build errors. [openvdb]Upgrade version to 6.1.0 Jun 12, 2019
Merge branch 'master' of https://github.com/microsoft/vcpkg into dev/…
d65e8f2 
…jack/upgrade_openvdb_6.1.0

# Conflicts:
#	ports/openvdb/CONTROL
@Rastaban Rastaban merged commit eff0769 into microsoft:master Jun 26, 2019
pull bot pushed a commit to harrysummer/vcpkg that referenced this pull request Jun 26, 2019
@JackBoosY @pull
[openvdb]Upgrade version to 6.1.0, regenerate patches and fix build e…
8f01345 
…rrors. (microsoft#6864)
@JackBoosY JackBoosY deleted the dev/jack/upgrade_openvdb_6.1.0 branch June 27, 2019 02:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@Rastaban Rastaban

@grdowns grdowns

Labels
info:internal This PR or Issue was filed by the vcpkg team.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@JackBoosY @Rastaban @grdowns