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

[CGNS/ParaView] Add new ports #9960

Merged
merged 26 commits into from
Jun 23, 2020
Merged

Conversation

Neumann-A
Copy link
Contributor

@Neumann-A Neumann-A commented Feb 7, 2020

loses #9765 should be seperate PR
closes #5330
closes #11331
closes #9180

TODO:

  • Check features and other Platforms.
  • Check remaining Patches.
  • Python feature + patches.
  • Redo Qt static plugin patches. (if desired. are not required starting with Qt 5.14)

Current Status: Should built and install. Might fail within portfile or post build checks.

@MVoz
Copy link
Contributor

MVoz commented Mar 1, 2020

vcpkg install CGNS[*]:x64-windows

Package hdf5 does not have a mpi feature

there is no mpi support word in hdf5, there is a parallel

vcpkg install hdf5[core,parallel,szip,tools,zlib]:x64-windows

Build-Depends: hdf5[mpi] -->> hdf5[parallel]

vcpkg install cgns[core,hdf5,legacy,lfs,lfsselector,tools]:x64-windows --recurse
Computing installation plan...
The following packages will be built and installed:
    cgns[core,hdf5,legacy,lfs,lfsselector,tools]:x64-windows
Starting package 1/1: cgns:x64-windows
Building package cgns[core,hdf5,legacy,lfs,lfsselector,tools]:x64-windows...
-- Using cached E:/tools/vcpkg/downloads/CGNS-CGNS-3420e23febf0eb38c1b05af3c157d614d8476557.tar.gz
-- Using source at E:/tools/vcpkg/buildtrees/cgns/src/14d8476557-c37af86822
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Installing: E:/tools/vcpkg/packages/cgns_x64-windows/share/cgns/cgnsBuild.defs
-- Installing: E:/tools/vcpkg/packages/cgns_x64-windows/include/cgnsconfig.h
-- Installing: E:/tools/vcpkg/packages/cgns_x64-windows/tools/cgns/cgnscheck.exe
-- Installing: E:/tools/vcpkg/packages/cgns_x64-windows/tools/cgns/cgnscompress.exe
-- Installing: E:/tools/vcpkg/packages/cgns_x64-windows/tools/cgns/cgnsconvert.exe
-- Installing: E:/tools/vcpkg/packages/cgns_x64-windows/tools/cgns/cgnsdiff.exe
-- Installing: E:/tools/vcpkg/packages/cgns_x64-windows/tools/cgns/cgnslist.exe
-- Installing: E:/tools/vcpkg/packages/cgns_x64-windows/tools/cgns/cgnsnames.exe
-- Installing: E:/tools/vcpkg/packages/cgns_x64-windows/share/cgns/copyright
-- Performing post-build validation
-- Performing post-build validation done
Building package cgns[core,hdf5,legacy,lfs,lfsselector,tools]:x64-windows... done
Installing package cgns[core,hdf5,legacy,lfs,lfsselector,tools]:x64-windows...
Installing package cgns[core,hdf5,legacy,lfs,lfsselector,tools]:x64-windows... done

@JackBoosY
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Pull request contains merge conflicts.

@Neumann-A
Copy link
Contributor Author

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.

@JackBoosY
Copy link
Contributor

@Neumann-A I think it has something to do with building queues.

@larshg
Copy link
Contributor

larshg commented Mar 18, 2020

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.

@Neumann-A
Copy link
Contributor Author

@larshg On windows according to CI and my tests this should just work fine. Linux and OSX CI are kind of a problem.

@larshg
Copy link
Contributor

larshg commented Mar 18, 2020

@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?
Is it possible to use 8.2 for starters?
Else I have to start working on this :)

@Neumann-A
Copy link
Contributor Author

@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.
It is not head of VTK but the version used by PV release 5.7 which seems to be good enough for a ParaView release; ) Unfortunately the different VTK/ITK/PV/vtk-m/etc. don't coordinate their release tags/schedules although I saw somewhere on their gitlab an issue about that and a plan to make coordinates releases in the future.

@larshg
Copy link
Contributor

larshg commented Mar 19, 2020

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?

@Neumann-A
Copy link
Contributor Author

@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.

@larshg
Copy link
Contributor

larshg commented Mar 19, 2020

@Neumann-A Okay, maybe I'll try look into it.

@JackBoosY
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Pull request contains merge conflicts.

@JackBoosY
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Pull request contains merge conflicts.

1 similar comment
@azure-pipelines
Copy link

Pull request contains merge conflicts.

@JackBoosY
Copy link
Contributor

Please resolve conflicts.

Thanks.

@Neumann-A Neumann-A force-pushed the extract_paraview_pr branch from fcbb89e to 38bb147 Compare May 11, 2020 20:59
@Neumann-A Neumann-A changed the title [VTK-m/VTK/ParaView] Add new port (might work now) [ParaView] Add new port (might work now) May 11, 2020
ports/paraview/CONTROL Outdated Show resolved Hide resolved
@JackBoosY
Copy link
Contributor

@Neumann-A Just replace the label name.

@JackBoosY JackBoosY added requires:testing Needs tests added before merging and removed requires:discussion labels May 22, 2020
@JackBoosY
Copy link
Contributor

When building cgns[mpi,fortran,tests,tools,hdf5,lfsselector,lfs,legacy]:

CMake Error at CMakeLists.txt:117 (enable_language):
  The Ninja generator does not support Fortran using Ninja version

    1.8.2

  due to lack of required features.  Kitware has implemented the required
  features but as of this version of CMake they have not been integrated to
  upstream ninja.  Pending integration, Kitware maintains a branch at:

    https://github.com/Kitware/ninja/tree/features-for-fortran#readme

  with the required features.  One may build ninja from that branch to get
  support for Fortran.

Should we update ninja version?

@Neumann-A
Copy link
Contributor Author

@JackBoosY: internal version in vcpkg is already 1.10. vcpkg is picking up the wrong one for you

@JackBoosY
Copy link
Contributor

When building .\vcpkg.exe install vtk[vtkm,openvr,qt,mpi,python,atlmfc,paraview,cuda,all]:x64-windows:

CMake Error at CMake/vtkDownload.cmake:8 (message):
  Attempted to download Module_MomentInvariants when VTK_FORBID_DOWNLOADS is
  ON
Call Stack (most recent call first):
  CMake/vtkModuleRemote.cmake:142 (vtk_download_attempt_check)
  Remote/MomentInvariants.remote.cmake:5 (vtk_fetch_module)
  Remote/CMakeLists.txt:9 (include)

@mathstuf
Copy link

mathstuf commented Jun 5, 2020

9.0.1 will have this patch which allows you to fix that: https://gitlab.kitware.com/vtk/vtk/-/merge_requests/6914

@Neumann-A
Copy link
Contributor Author

@JackBoosY: VTK_FORBID_DOWNLOADS was already there before I touched the port. Git blame tells me that @ras0219-msft was the one adding it in 3ee7045. I don't really know why because VTKs remote module seems to be locked to a certain version. So turning it on should not be a problem.
This probably also means that the all feature has been broken for a long time within master and should not block this PR.

@mathstuf
Copy link

mathstuf commented Jun 5, 2020

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 :) .

@JackBoosY JackBoosY added info:reviewed Pull Request changes follow basic guidelines requires:discussion and removed requires:testing Needs tests added before merging labels Jun 8, 2020
Copy link
Contributor

@dan-shaw dan-shaw left a 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

@JackBoosY
Copy link
Contributor

Please resolve the file conflicts.

# Conflicts:
#	ports/vtk/CONTROL
#	ports/vtk/portfile.cmake
@Neumann-A
Copy link
Contributor Author

@JackBoosY: Done

@JackBoosY JackBoosY added info:reviewed Pull Request changes follow basic guidelines and removed info:reviewed Pull Request changes follow basic guidelines labels Jun 12, 2020
@dan-shaw dan-shaw merged commit 03766d0 into microsoft:master Jun 23, 2020
@Neumann-A Neumann-A deleted the extract_paraview_pr branch June 23, 2020 17:58
@Neumann-A Neumann-A mentioned this pull request Jul 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:new-port The issue is requesting a new library to be added; consider making a PR! info:reviewed Pull Request changes follow basic guidelines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[opencv3[vtk]] build failure [New Port Request] ParaView [New port request] Paraview
9 participants