VTK issueshttps://gitlab.kitware.com/vtk/vtk/-/issues2021-11-23T12:38:42-05:00https://gitlab.kitware.com/vtk/vtk/-/issues/183919.1.0: Fails to build: ThirdParty/hdf5/vtkhdf5/src/H5make_libsettings.c inclu...2021-11-23T12:38:42-05:00yurivict9.1.0: Fails to build: ThirdParty/hdf5/vtkhdf5/src/H5make_libsettings.c includes sys/file.h which isn't defined by POSIX-1.2008 but is compiled with -D_POSIX_C_SOURCE=200809LThis command fails:
> /usr/bin/cc -D_POSIX_C_SOURCE=200809L -I/disk-samsung/freebsd-ports/math/vtk9/work/VTK-9.1.0/ThirdParty/hdf5/vtkhdf5/src -I/disk-samsung/freebsd-ports/math/vtk9/work/.build/ThirdParty/hdf5/vtkhdf5/src -std=c99 -O2 -...This command fails:
> /usr/bin/cc -D_POSIX_C_SOURCE=200809L -I/disk-samsung/freebsd-ports/math/vtk9/work/VTK-9.1.0/ThirdParty/hdf5/vtkhdf5/src -I/disk-samsung/freebsd-ports/math/vtk9/work/.build/ThirdParty/hdf5/vtkhdf5/src -std=c99 -O2 -pipe -fno-omit-frame-pointer -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -O2 -pipe -fno-omit-frame-pointer -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -fPIE -std=gnu99 -MD -MT ThirdParty/hdf5/vtkhdf5/src/CMakeFiles/H5make_libsettings.dir/H5make_libsettings.c.o -c /disk-samsung/freebsd-ports/math/vtk9/work/VTK-9.1.0/ThirdParty/hdf5/vtkhdf5/src/H5make_libsettings.c
```
/usr/include/sys/file.h:233:2: error: unknown type name 'u_int'
u_int xf_flag; /* flags (see fcntl.h) */
^
1 error generated.
```
Downstream bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259975
Version: 9.1.0
OS: FreeBSD 13https://gitlab.kitware.com/vtk/vtk/-/issues/192329.3.0 fails to compile: error: incompatible function pointer types passing 'h...2024-03-22T08:39:33-04:00yurivict9.3.0 fails to compile: error: incompatible function pointer types passing 'herr_t (hid_t, const char *, const H5L_info2_t *, void *)' (aka 'int (long, const char *, const H5L_info2_t *, void *)') to parameter of type 'H5L_iterate1_t' (aka 'int (*)(long,```
/usr/ports/math/vtk9/work/VTK-9.3.0/ThirdParty/cgns/vtkcgns/src/adfh/ADFH.c:1127:34: warning: incompatible pointer types passing 'H5L_info2_t *' to parameter of type 'H5L_info1_t *' [-Wincompatible-pointer-types]
herr = H5Lget_info...```
/usr/ports/math/vtk9/work/VTK-9.3.0/ThirdParty/cgns/vtkcgns/src/adfh/ADFH.c:1127:34: warning: incompatible pointer types passing 'H5L_info2_t *' to parameter of type 'H5L_info1_t *' [-Wincompatible-pointer-types]
herr = H5Lget_info(id, D_LINK, &sb, H5P_DEFAULT);
^~~
/usr/local/include/H5Lpublic.h:1703:73: note: passing argument to parameter 'linfo' here
H5_DLL herr_t H5Lget_info1(hid_t loc_id, const char *name, H5L_info1_t *linfo /*out*/, hid_t lapl_id);
^
/usr/ports/math/vtk9/work/VTK-9.3.0/ThirdParty/cgns/vtkcgns/src/adfh/ADFH.c:1287:92: error: incompatible function pointer types passing 'herr_t (hid_t, const char *, const H5L_info2_t *, void *)' (aka 'int (long, const char *, const H5L_info2_t *, void *)') to parameter of type 'H5L_iterate1_t' (aka 'int (*)(long, const char *, const H5L_info1_t *, void *)') [-Wincompatible-function-pointer-types]
if (! is_link(id)) H5Literate_by_name(id, name, H5_INDEX_CRT_ORDER, H5_ITER_INC, NULL, delete_children, data, H5P_DEFAULT);
^~~~~~~~~~~~~~~
/usr/local/include/H5Lpublic.h:1908:87: note: passing argument to parameter 'op' here
H5_iter_order_t order, hsize_t *idx, H5L_iterate1_t op, void *op_data,
^
/usr/ports/math/vtk9/work/VTK-9.3.0/ThirdParty/cgns/vtkcgns/src/adfh/ADFH.c:1447:63: error: incompatible function pointer types passing 'herr_t (hid_t, const char *, const H5L_info2_t *, void *)' (aka 'int (long, const char *, const H5L_info2_t *, void *)') to parameter of type 'H5L_iterate1_t' (aka 'int (*)(long, const char *, const H5L_info1_t *, void *)') [-Wincompatible-function-pointer-types]
H5Literate(gid, H5_INDEX_CRT_ORDER, H5_ITER_NATIVE, NULL, fix_dimensions, NULL);
^~~~~~~~~~~~~~
/usr/local/include/H5Lpublic.h:1835:42: note: passing argument to parameter 'op' here
H5L_iterate1_t op, void *op_data);
^
/usr/ports/math/vtk9/work/VTK-9.3.0/ThirdParty/cgns/vtkcgns/src/adfh/ADFH.c:1542:65: error: incompatible function pointer types passing 'herr_t (hid_t, const char *, const H5L_info2_t *, void *)' (aka 'int (long, const char *, const H5L_info2_t *, void *)') to parameter of type 'H5L_iterate1_t' (aka 'int (*)(long, const char *, const H5L_info1_t *, void *)') [-Wincompatible-function-pointer-types]
!H5Literate(hpid, H5_INDEX_CRT_ORDER, H5_ITER_NATIVE, NULL, compare_children, (void *)&stat)) {
^~~~~~~~~~~~~~~~
/usr/local/include/H5Lpublic.h:1835:42: note: passing argument to parameter 'op' here
H5L_iterate1_t op, void *op_data);
```
Version: 9.3.0
clang-16
FreeBSD 14.0https://gitlab.kitware.com/vtk/vtk/-/issues/18397[feature suggestion] cmake should print all groups/modules that are enabled o...2021-11-24T07:16:31-05:00yurivict[feature suggestion] cmake should print all groups/modules that are enabled or disabledOtherwise there's no easy visibility of what is being built and what isn't being built.Otherwise there's no easy visibility of what is being built and what isn't being built.https://gitlab.kitware.com/vtk/vtk/-/issues/17527[Module] VTK_BUILD_TESTING and BUILD_TESTING options available in ccmake or c...2019-03-05T04:38:04-05:00Mathieu Westphal (Kitware)[Module] VTK_BUILD_TESTING and BUILD_TESTING options available in ccmake or cmake-guiThere are two options available in ccmake and cmake-gui, `VTK_BUILD_TESTING` and `BUILD_TESTING`.
`BUILD_TESTING` should be hidden.
this bug is also present in ParaView.
@ben.boeckelThere are two options available in ccmake and cmake-gui, `VTK_BUILD_TESTING` and `BUILD_TESTING`.
`BUILD_TESTING` should be hidden.
this bug is also present in ParaView.
@ben.boeckelBen BoeckelBen Boeckelhttps://gitlab.kitware.com/vtk/vtk/-/issues/17876[VTK 9.0] Building with external PEGTL not working.2021-05-15T15:29:23-04:00Alexander Neumann[VTK 9.0] Building with external PEGTL not working.`-- Found PEGTL: D:/qt2/installed/x64-windows/include/tao (found suitable version "3.0.0", minimum required is "2.0.0") `
Error:
```
FAILED: IO/MotionFX/CMakeFiles/IOMotionFX.dir/vtkMotionFXCFGReader.cxx.obj
C:\PROGRA~2\MIB055~1\2019\C...`-- Found PEGTL: D:/qt2/installed/x64-windows/include/tao (found suitable version "3.0.0", minimum required is "2.0.0") `
Error:
```
FAILED: IO/MotionFX/CMakeFiles/IOMotionFX.dir/vtkMotionFXCFGReader.cxx.obj
C:\PROGRA~2\MIB055~1\2019\COMMUN~1\VC\Tools\MSVC\1425~1.286\bin\Hostx64\x64\cl.exe /TP -DIOMotionFX_EXPORTS -DVTK_IN_VTK -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS -D_SCL_SECURE_NO_DEPRECATE -D_SCL_SECURE_NO_WARNINGS -IIO\MotionFX -ID:\qt2\buildtrees\vtk\src\a3ddafb3ad-6f3d1d5aad\IO\MotionFX -ICommon\ExecutionModel -ID:\qt2\buildtrees\vtk\src\a3ddafb3ad-6f3d1d5aad\Common\ExecutionModel -ICommon\Core -ID:\qt2\buildtrees\vtk\src\a3ddafb3ad-6f3d1d5aad\Common\Core -ICommon\DataModel -ID:\qt2\buildtrees\vtk\src\a3ddafb3ad-6f3d1d5aad\Common\DataModel -ICommon\Math -ID:\qt2\buildtrees\vtk\src\a3ddafb3ad-6f3d1d5aad\Common\Math -ICommon\Transforms -ID:\qt2\buildtrees\vtk\src\a3ddafb3ad-6f3d1d5aad\Common\Transforms -ICommon\Misc -ID:\qt2\buildtrees\vtk\src\a3ddafb3ad-6f3d1d5aad\Common\Misc -IIO\Geometry -ID:\qt2\buildtrees\vtk\src\a3ddafb3ad-6f3d1d5aad\IO\Geometry -IIO\Core -ID:\qt2\buildtrees\vtk\src\a3ddafb3ad-6f3d1d5aad\IO\Core -IIO\Legacy -ID:\qt2\buildtrees\vtk\src\a3ddafb3ad-6f3d1d5aad\IO\Legacy -IUtilities\KWIML -ID:\qt2\buildtrees\vtk\src\a3ddafb3ad-6f3d1d5aad\Utilities\KWIML -IUtilities\KWSys -ID:\qt2\buildtrees\vtk\src\a3ddafb3ad-6f3d1d5aad\Utilities\KWSys -IThirdParty\pegtl -ID:\qt2\buildtrees\vtk\src\a3ddafb3ad-6f3d1d5aad\ThirdParty\pegtl -ID:\qt2\installed\x64-windows\include\tao /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /GR /EHsc /MP /DVCPKG_IS_COOL /bigobj /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1 /DVCPKG_IS_COOL_DEBUG /showIncludes /FoIO\MotionFX\CMakeFiles\IOMotionFX.dir\vtkMotionFXCFGReader.cxx.obj /FdIO\MotionFX\CMakeFiles\IOMotionFX.dir\ /FS -c D:\qt2\buildtrees\vtk\src\a3ddafb3ad-6f3d1d5aad\IO\MotionFX\vtkMotionFXCFGReader.cxx
D:\qt2\buildtrees\vtk\x64-windows-dbg\ThirdParty\pegtl\vtk_pegtl.h(28): fatal error C1083: Cannot open include file: 'tao/pegtl.hpp': No such file or directory
```
Currently trying to figure out why it is not using the include folderhttps://gitlab.kitware.com/vtk/vtk/-/issues/17893[VTK 9.0] Common/DataModel/vtkCompositeDataSetNodeReference.h not getting ins...2020-05-14T09:56:51-04:00Alexander Neumann[VTK 9.0] Common/DataModel/vtkCompositeDataSetNodeReference.h not getting installedRequired by `vtkDataObjectTreeRange.h` which gets installed. Discovered by building Paraview 5.8 with external VTKRequired by `vtkDataObjectTreeRange.h` which gets installed. Discovered by building Paraview 5.8 with external VTK9.0.1Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/vtk/vtk/-/issues/17878[VTK 9.0] Fails with hdf5-config.cmake2021-06-01T15:35:05-04:00Alexander Neumann[VTK 9.0] Fails with hdf5-config.cmakeFirst error of many:
```
CMake Error at /mnt/d/qt2/scripts/buildsystems/vcpkg.cmake:250 (_add_library):
Target "exodusII" links to target "hdf5::hdf5-static" but the target was
not found. Perhaps a find_package() call is missing for...First error of many:
```
CMake Error at /mnt/d/qt2/scripts/buildsystems/vcpkg.cmake:250 (_add_library):
Target "exodusII" links to target "hdf5::hdf5-static" but the target was
not found. Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
Call Stack (most recent call first):
CMake/vtkModule.cmake:3328 (add_library)
ThirdParty/exodusII/vtkexodusII/CMakeLists.txt:300 (vtk_module_add_module)
```
Output of configure:
```
-- Found HDF5 at /mnt/d/qt2/installed/x64-linux/share/hdf5 via NO_MODULE. Now trying to extract locations etc.
-- Trying to get properties of target hdf5::hdf5-static
-- Found imported configurations: DEBUG;RELEASE
-- Start search through imported configurations in the following order: Debug;RELWITHDEBINFO;RELEASE;DEBUG;DEBUG
-- Selected imported configuration: RELEASE
-- Found HDF5: hdf5::hdf5-static (found version "1.10.5") found components: C HL
-- HDF5_DIR: /mnt/d/qt2/installed/x64-linux/share/hdf5
-- HDF5_DEFINITIONS:
-- HDF5_INCLUDE_DIRS: /mnt/d/qt2/installed/x64-linux/include
-- HDF5_LIBRARIES: hdf5::hdf5-static
-- HDF5_HL_LIBRARIES: hdf5::hdf5_hl-static
-- HDF5_C_DEFINITIONS:
-- HDF5_C_INCLUDE_DIR:
-- HDF5_C_INCLUDE_DIRS: /mnt/d/qt2/installed/x64-linux/include
-- HDF5_C_LIBRARY: /mnt/d/qt2/installed/x64-linux/lib/libhdf5.a
-- HDF5_C_LIBRARIES: hdf5::hdf5-static
-- HDF5_C_HL_LIBRARY: /mnt/d/qt2/installed/x64-linux/lib/libhdf5_hl.a
-- HDF5_C_HL_LIBRARIES: hdf5::hdf5_hl-static
```
Probably needs to add `set_target_properties(hdf5::hdf5-(shared|static) PROPERTIES IMPORTED_GLOBAL TRUE)` and `set_target_properties(hdf5::hdf5_hl-(shared|static) PROPERTIES IMPORTED_GLOBAL TRUE)`https://gitlab.kitware.com/vtk/vtk/-/issues/17895[VTK 9.0] Find(LibHaru|LZMA).cmake cannot correctly handle finding both DEBUG...2020-05-14T09:56:05-04:00Alexander Neumann[VTK 9.0] Find(LibHaru|LZMA).cmake cannot correctly handle finding both DEBUG and RELEASE librariesError:
```
-- Found LibHaru: optimized;D:/para/installed/x64-windows/lib/libhpdf.lib;debug;D:/para/installed/x64-windows/debug/lib/libhpdfd.lib (found suitable version "2.4.0-dev", minimum required is "2.4.0")
CMake Error at CMake/vtkDe...Error:
```
-- Found LibHaru: optimized;D:/para/installed/x64-windows/lib/libhpdf.lib;debug;D:/para/installed/x64-windows/debug/lib/libhpdfd.lib (found suitable version "2.4.0-dev", minimum required is "2.4.0")
CMake Error at CMake/vtkDetectLibraryType.cmake:31 (message):
Unparsed arguments for vtk_detect_library_type:
D:/para/installed/x64-windows/lib/libhpdf.lib;debug;D:/para/installed/x64-windows/debug/lib/libhpdfd.lib
Call Stack (most recent call first):
CMake/FindLibHaru.cmake:48 (vtk_detect_library_type)
D:/para/scripts/buildsystems/vcpkg.cmake:329 (_find_package)
CMake/vtkModule.cmake:4134 (find_package)
CMake/vtkModule.cmake:4690 (vtk_module_find_package)
CMake/vtkModule.cmake:4564 (vtk_module_third_party_external)
ThirdParty/libharu/CMakeLists.txt:1 (vtk_module_third_party)
```Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/vtk/vtk/-/issues/17875[VTK 9.0] Ninja build error with external vtk-m2020-05-04T08:41:31-04:00Alexander Neumann[VTK 9.0] Ninja build error with external vtk-mError:
`ninja: error: build.ninja:96011: unknown pool name 'vtkm_pool'`
Probable reason:
```
vtk_module_set_property(VTK::AcceleratorsVTKm
PROPERTY JOB_POOL_COMPILE
VALUE vtkm_pool)
```
Can I simply patch that out?Error:
`ninja: error: build.ninja:96011: unknown pool name 'vtkm_pool'`
Probable reason:
```
vtk_module_set_property(VTK::AcceleratorsVTKm
PROPERTY JOB_POOL_COMPILE
VALUE vtkm_pool)
```
Can I simply patch that out?https://gitlab.kitware.com/vtk/vtk/-/issues/17898[VTK 9.0] Unable to pass Python3_LIBRARY_<CONFIG> or Python3_LIBRARIES via CMake2020-05-29T10:18:57-04:00Alexander Neumann[VTK 9.0] Unable to pass Python3_LIBRARY_<CONFIG> or Python3_LIBRARIES via CMakethe find module seems to simply ignore these. Would be nice if it did not do that or not use `_Python3_LIBRARY_RELEASE` as a hint for `_Python3_LIBRARY_DEBUG` and do a search with `NO_DEFAULT_PATH` on windows.the find module seems to simply ignore these. Would be nice if it did not do that or not use `_Python3_LIBRARY_RELEASE` as a hint for `_Python3_LIBRARY_DEBUG` and do a search with `NO_DEFAULT_PATH` on windows.https://gitlab.kitware.com/vtk/vtk/-/issues/16831`VTK_USE_BOOST` is obsolete in vtkInfovisBoostGraphAlgorithms2019-03-21T21:03:12-04:00Haocheng LIU`VTK_USE_BOOST` is obsolete in vtkInfovisBoostGraphAlgorithmsThe problem is that the usage of **vtkInfovisBoostGraphAlgorithm** module is dependent on `VTK_USE_BOOST` being defined during the build, but it's defined nowhere. Without boost library, it would never work.
See line 18 of file [vtkCos...The problem is that the usage of **vtkInfovisBoostGraphAlgorithm** module is dependent on `VTK_USE_BOOST` being defined during the build, but it's defined nowhere. Without boost library, it would never work.
See line 18 of file [vtkCosmicTreelayoutStrategy.cxx](https://gitlab.kitware.com/vtk/vtk/blob/master/Infovis/Layout/vtkCosmicTreeLayoutStrategy.cxx).
After discussing with Ben and David Thompson, here is a potential solution:
In pre-VTK-6 releases, one way of dealing with missing library dependencies (i.e., no boost) was to compile the class but have it do nothing. That it the way vtkCosmicTreeLayoutStrategy was written. The VTK_USE_BOOST tests should be removed (so that it will only compile when boost is present) and the class added to a module that is only compiled when boost is present.
It looks like all of these classes need the same treatment:
Layout/vtkCosmicTreeLayoutStrategy.cxx
Layout/vtkTreeLayoutStrategy.cxx
Layout/vtkTreeOrbitLayoutStrategy.cxx
I would recommend adding a VTK/Infovis/BoostLayout module that depends on vtkInfovisLayout and boost; putting all of these classes in it; and removing the VTK_USE_BOOST #ifdefs.Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/vtk/vtk/-/issues/17650Add a buildbot dedicated to build kitware-maintained VTK dependent software w...2019-07-26T07:08:42-04:00Mathieu Westphal (Kitware)Add a buildbot dedicated to build kitware-maintained VTK dependent software with VTK masterIn order to anticipate and avoid the pain caused to developper that uses VTK, it would be nice to have a buildbot dedicated to build VTK dependant software.
These builds will not cover all usecases, but a rather generic standard one.
Pa...In order to anticipate and avoid the pain caused to developper that uses VTK, it would be nice to have a buildbot dedicated to build VTK dependant software.
These builds will not cover all usecases, but a rather generic standard one.
ParaView, CMB, Tomviz and Slicer come to mind.
@ben.boeckel @utkarsh.ayachithttps://gitlab.kitware.com/vtk/vtk/-/issues/17314Add liblz4 to library search names in FindLZ4.cmake2019-05-31T10:03:05-04:00jakirkhamAdd liblz4 to library search names in FindLZ4.cmakeWould be nice to include `liblz4` in addition to `lz4` in the library names searched for by `FindLZ4.cmake`.Would be nice to include `liblz4` in addition to `lz4` in the library names searched for by `FindLZ4.cmake`.Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/vtk/vtk/-/issues/17836Add ORDER_DEPENDS for modules2020-04-08T15:53:24-04:00Ben BoeckelAdd ORDER_DEPENDS for modulesSometimes a module must be built before another, but is not needed for linking. In #17835, it is due to CMake variables only guaranteed to be set in that module which end up being used elsewhere.
Cc: @utkarsh.ayachit @brad.king @robertm...Sometimes a module must be built before another, but is not needed for linking. In #17835, it is due to CMake variables only guaranteed to be set in that module which end up being used elsewhere.
Cc: @utkarsh.ayachit @brad.king @robertmaynardBen BoeckelBen Boeckelhttps://gitlab.kitware.com/vtk/vtk/-/issues/18471Add tests to verify that third party libraries are mangled2022-02-16T15:14:04-05:00Ben BoeckelAdd tests to verify that third party libraries are mangledThere should be tests to ensure that all public symbols in third party libraries are properly mangled.
Cc: @seanmThere should be tests to ensure that all public symbols in third party libraries are properly mangled.
Cc: @seanmhttps://gitlab.kitware.com/vtk/vtk/-/issues/18032Add VTK_USE_COCOA and VTK_USE_X to VTK config file2020-11-09T14:13:44-05:00Jean-Christophe Fillion-RobinAdd VTK_USE_COCOA and VTK_USE_X to VTK config fileWhen building LookingGlassVTKModule externally (thanks to [PR Kitware/LookingGlassVTKModule#9](https://github.com/Kitware/LookingGlassVTKModule/pull/9), it fails to include `vtkCocoaLookingGlassRenderWindow.mm` and `vtkCocoaLookingGlassR...When building LookingGlassVTKModule externally (thanks to [PR Kitware/LookingGlassVTKModule#9](https://github.com/Kitware/LookingGlassVTKModule/pull/9), it fails to include `vtkCocoaLookingGlassRenderWindow.mm` and `vtkCocoaLookingGlassRenderWindow.h` (see [here](https://github.com/Kitware/LookingGlassVTKModule/blob/f3b4c8928c002533337479733af4ec10282c7aa9/CMakeLists.txt#L13-L16) and issue [KitwareMedical/SlicerLookingGlass#2](https://github.com/KitwareMedical/SlicerLookingGlass/issues/2))
Moving forward, I would like to expose option like `VTK_USE_COCOA` and `VTK_USE_X` into a config file.
What is the CMake equivalent of `vtkRenderingOpenGLConfigure.h` ?Jean-Christophe Fillion-RobinJean-Christophe Fillion-Robinhttps://gitlab.kitware.com/vtk/vtk/-/issues/16967Android link error2018-10-23T13:54:47-04:00SchroediAndroid link errorI am unable to build the android samples with VTK 7.1(or current master) as the build system tries to link ``/usr/lib32/libGLU.so`` to the android arm library.
This problem also occurs when linking my own application with VTK. The same...I am unable to build the android samples with VTK 7.1(or current master) as the build system tries to link ``/usr/lib32/libGLU.so`` to the android arm library.
This problem also occurs when linking my own application with VTK. The same steps work for the 7.0 tag.
# Steps to reproduce
```bash
git checkout v7.1.0
mkdir build && cd build
ANDROID_NDK=/opt/android-sdk-linux/ndk-bundle/ cmake .. -DVTK_ANDROID_BUILD=ON -DBUILD_EXAMPLES=ON
make -j8
```
# Result
``[100%] Built target vtkRenderingOpenGL2
Scanning dependencies of target JavaVTK
Scanning dependencies of target NativeVTK
[100%] Building CXX object Examples/Android/JavaVTK/jni/CMakeFiles/JavaVTK.dir/main.cxx.o
[100%] Building C object Examples/Android/NativeVTK/jni/CMakeFiles/NativeVTK.dir/home/ascadian/Installs/android-sdk-linux/ndk-bundle/sources/android/native_app_glue/android_native_app_glue.c.o
[100%] Building CXX object Examples/Android/NativeVTK/jni/CMakeFiles/NativeVTK.dir/main.cxx.o
[100%] Linking CXX shared library ../libs/armeabi/libJavaVTK.so
[100%] Linking CXX shared library ../libs/armeabi/libNativeVTK.so
/home/ascadian/Installs/android-sdk-linux/ndk-bundle/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.9.x/../../../../arm-linux-androideabi/bin/ld: error: /usr/lib32/libGLU.so: incompatible target
collect2: error: ld returned 1 exit status
make[5]: *** [Examples/Android/JavaVTK/jni/CMakeFiles/JavaVTK.dir/build.make:149: Examples/Android/JavaVTK/libs/armeabi/libJavaVTK.so] Error 1
make[4]: *** [CMakeFiles/Makefile2:3715: Examples/Android/JavaVTK/jni/CMakeFiles/JavaVTK.dir/all] Error 2
make[4]: *** Waiting for unfinished jobs....
/home/ascadian/Installs/android-sdk-linux/ndk-bundle/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.9.x/../../../../arm-linux-androideabi/bin/ld: error: /usr/lib32/libGLU.so: incompatible target
collect2: error: ld returned 1 exit status
make[5]: *** [Examples/Android/NativeVTK/jni/CMakeFiles/NativeVTK.dir/build.make:181: Examples/Android/NativeVTK/libs/armeabi/libNativeVTK.so] Error 1
make[4]: *** [CMakeFiles/Makefile2:3491: Examples/Android/NativeVTK/jni/CMakeFiles/NativeVTK.dir/all] Error 2
make[3]: *** [Makefile:128: all] Error 2
make[2]: *** [CMakeFiles/vtk-android.dir/build.make:112: CMakeExternals/Prefix/vtk-android-21-armeabi/src/vtk-android-stamp/vtk-android-build] Error 2
make[1]: *** [CMakeFiles/Makefile2:68: CMakeFiles/vtk-android.dir/all] Error 2
make: *** [Makefile:95: all] Error 2``
# Expected result
Sample apks should be build as they are with v7.0 after patching a missing ``#include <android/native_window.h>``.https://gitlab.kitware.com/vtk/vtk/-/issues/17018API/ABI changes review for VTK2018-10-23T13:27:33-04:00AndreyAPI/ABI changes review for VTKMay be useful for tracking API/ABI changes in the library: https://abi-laboratory.pro/tracker/timeline/vtk/
The report is created with the help of open-source abi-tracker tool: https://github.com/lvc/abi-tracker
Thank you.
![VTK-1](/...May be useful for tracking API/ABI changes in the library: https://abi-laboratory.pro/tracker/timeline/vtk/
The report is created with the help of open-source abi-tracker tool: https://github.com/lvc/abi-tracker
Thank you.
![VTK-1](/uploads/44ef82c37ffd161b452a3619784da9d4/VTK-1.png)
![VTK-2](/uploads/dba15318db971d0dde0ee73b6f3e9e3e/VTK-2.png)
## Environment
* Linux x86_64
* GCC 4.9
* VTK 6.2.0 and higherhttps://gitlab.kitware.com/vtk/vtk/-/issues/19047Bad module dependency for vtkGenerateTimeSteps2023-08-22T09:22:33-04:00Charly BollingerBad module dependency for vtkGenerateTimeSteps## Description
The useful `vtkGenerateTimeSteps` filter can be found in the `VTK::FiltersHybrid` module. Several sources could need this filter to avoid code duplication, if they wanted the source to allow time steps generation. This is...## Description
The useful `vtkGenerateTimeSteps` filter can be found in the `VTK::FiltersHybrid` module. Several sources could need this filter to avoid code duplication, if they wanted the source to allow time steps generation. This is the case of the `vtkTimeSourceExample` and the more recent `vtkSpatioTemporalHarmonicsSource`.
However, the `VTK::FiltersHybrid` module implies adding strong dependencies, such as the `VTK::RenderingCore` module. This would be bad to need the rendering module to be able to create sources.
## Possible fixes
From the best to the worst solution imo:
* The `vtkGenerateTimeSteps` filter should be moved out of this module, in a better fitting module such as `VTK::FiltersCore` or `VTK::FiltersGeneral`.
* The `VTK::FiltersHybrid` module should move every filter depending on rendering in a more appropriate module, to remove the `VTK::RenderingCore` module dependency.
* Sources needing the `vtkGenerateTimeSteps` filter should be moved in the `VTK::FiltersHybrid` module.https://gitlab.kitware.com/vtk/vtk/-/issues/17695bring back pypi wheels2020-06-16T09:09:55-04:00David E. DeMarlebring back pypi wheelsIn VTK 8.0 and 8.1, we built PyPi wheels for VTK via https://github.com/KitwareMedical/VTKPythonPackage.
8.2 broke the process. For 9.0 we should leverage the new CMake script infrastructure and set of automated tests to bring them back ...In VTK 8.0 and 8.1, we built PyPi wheels for VTK via https://github.com/KitwareMedical/VTKPythonPackage.
8.2 broke the process. For 9.0 we should leverage the new CMake script infrastructure and set of automated tests to bring them back sustainably.9.0.1T.J. CoronaT.J. Corona