-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[CGNS/ParaView] Add new ports #9960
Conversation
there is no mpi support word in hdf5, there is a parallel
Build-Depends: hdf5[mpi] -->> hdf5[parallel]
|
/azp run |
Pull request contains merge conflicts. |
hmmm Qt5X11Extras is still not building in CI..... so something is missing when it tries to build qt5-x11extras and it just does nothing but still succeeds. |
@Neumann-A I think it has something to do with building queues. |
What is the status of this - its getting tiresome, that VTK links to the wrong libraries. Can I help in any way? Using VS2019 on windows. |
@larshg On windows according to CI and my tests this should just work fine. Linux and OSX CI are kind of a problem. |
@Neumann-A I have merged this PR and is at least build sucessfully, but I noticed i says 8.9 - is it head of VTK that get compiled? |
@larshg: No PV does not compile with VTK 8.2 due to changes in API. Furthermore they completely rewrote their CMake module system so that it correctly works with CMake targets. |
So there won't be any correct Cmake configs for the 8.2 version, that is currently present in VCPKG I guess? Even after this is merged? |
@larshg: At least not from me. I am not going to fix the VTK 8.2 CMake mess, I once tried but gave up due to the amount of thinks which needed to be fixed. But I really like their new module system. |
@Neumann-A Okay, maybe I'll try look into it. |
/azp run |
Pull request contains merge conflicts. |
/azp run |
Pull request contains merge conflicts. |
1 similar comment
Pull request contains merge conflicts. |
Please resolve conflicts. Thanks. |
fcbb89e
to
38bb147
Compare
@Neumann-A Just replace the label name. |
When building
Should we update ninja version? |
@JackBoosY: internal version in vcpkg is already 1.10. vcpkg is picking up the wrong one for you |
When building
|
9.0.1 will have this patch which allows you to fix that: https://gitlab.kitware.com/vtk/vtk/-/merge_requests/6914 |
@JackBoosY: |
Note that I don't really consider the remote modules part of VTK. I want them to either be in VTK or out (especially now that VTK's install tree is much more well-behaved). Not this half way thing. But, politics are involved, so it's not a fast process :) . |
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.
LGTM, maybe needs another review
Please resolve the file conflicts. |
# Conflicts: # ports/vtk/CONTROL # ports/vtk/portfile.cmake
@JackBoosY: Done |
loses #9765should be seperate PRcloses #5330
closes #11331
closes #9180
TODO:
Current Status: Should built and install. Might fail within portfile or post build checks.