search

Kitware / TeleSculptor

TeleSculptor: Aerial Photogrammetry Application powered by KWIVER
Other
609 stars 149 forks source link

Flatpak TeleSculptor #425

Closed kevinsmia1939 closed 3 years ago

kevinsmia1939 commented 3 years ago

Hello,

I am trying to build Telesculptor for Linux Flatpak.

I got the error below. I build Kwiver 1.5.1 with cmake with the flags,

       -DCMAKE_BUILD_TYPE:STRING=Release
       -DKWIVER_ENABLE_SPROKIT=ON
       -DKWIVER_ENABLE_C_BINDINGS=ON
       -DKWIVER_ENABLE_TOOLS=ON

Build qtExtensions master branch with cmake with default flag. https://github.com/Kitware/qtextensions Build VTK 9.0.1 with cmake with these flags,

     -DBUILD_SHARED_LIBS=ON
     -DOpenGL_GL_PREFERENCE=GLVND
     -DCMAKE_BUILD_TYPE=Release
     -DVTK_PYTHON_VERSION:STRING=3
     -DVTK_GROUP_ENABLE_Qt=YES
     -DVTK_MODULE_ENABLE_VTK_GUISupportQt=YES
     -DModule_vtkGUISupportQtOpenGL:BOOL=ON

And finally Telesculptor 1.1.1 with Cmake.

       -DTELESCULPTOR_SUPERBUILD=OFF
       -DCMAKE_BUILD_TYPE:STRING=Release
       -DTELESCULPTOR_ENABLE_MANUALS=OFF
       -DTELESCULPTOR_ENABLE_TESTING=OFF

Could this issue be relate to this? https://github.com/Kitware/kwiver/issues/517

I got this error.

-- The C compiler identification is GNU 10.2.0
-- The CXX compiler identification is GNU 10.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for kwiver in : 
-- Current path: '/app/lib/cmake/kwiver;/run/build/telesculptor/CMake'
-- Import CMake future from '/app/lib/cmake/kwiver/future'
-- Import CMake future '3.10'
-- Found Doxygen: /usr/bin/doxygen (found version "1.9.1") found components: doxygen missing components: dot
-- Could NOT find Sphinx (missing: SPHINX_EXECUTABLE) 
-- Performing Test has_compiler_flag--std=cplusplus11
-- Performing Test has_compiler_flag--std=cplusplus11 - Success
-- Performing Test has_compiler_flag--pthread
-- Performing Test has_compiler_flag--pthread - Success
-- Performing Test has_compiler_flag--fvisibility=hidden
-- Performing Test has_compiler_flag--fvisibility=hidden - Success
-- Performing Test has_compiler_flag--Wall
-- Performing Test has_compiler_flag--Wall - Success
-- Performing Test has_compiler_flag--Werror=return-type
-- Performing Test has_compiler_flag--Werror=return-type - Success
-- Performing Test has_compiler_flag--Werror=non-virtual-dtor
-- Performing Test has_compiler_flag--Werror=non-virtual-dtor - Success
-- Performing Test has_compiler_flag--Werror=narrowing
-- Performing Test has_compiler_flag--Werror=narrowing - Success
-- Performing Test has_compiler_flag--Werror=init-self
-- Performing Test has_compiler_flag--Werror=init-self - Success
-- Performing Test has_compiler_flag--Werror=reorder
-- Performing Test has_compiler_flag--Werror=reorder - Success
-- Performing Test has_compiler_flag--Werror=overloaded-virtual
-- Performing Test has_compiler_flag--Werror=overloaded-virtual - Success
-- Performing Test has_compiler_flag--Werror=cast-qual
-- Performing Test has_compiler_flag--Werror=cast-qual - Success
-- Performing Test has_compiler_flag--Werror=vla
-- Performing Test has_compiler_flag--Werror=vla - Success
-- Performing Test has_compiler_flag--Wno-unknown-pragmas
-- Performing Test has_compiler_flag--Wno-unknown-pragmas - Success
-- Performing Test has_compiler_flag--Wl,--no-undefined
-- Performing Test has_compiler_flag--Wl,--no-undefined - Success
-- Performing Test has_compiler_flag--Wl,--copy-dt-needed-entries
-- Performing Test has_compiler_flag--Wl,--copy-dt-needed-entries - Success
-- checking CPP_AUTO auto.cxx
-- checking CPP_CONSTEXPR constexpr.cxx
-- checking CPP_DEFAULT_CTOR default-ctor.cxx
-- checking CPP_FINAL final.cxx
-- checking CPP_NOEXCEPT throw-noexcept.cxx
-- checking CPP_RANGE_FOR range-for.cxx
-- checking STD_CHRONO std_chrono.cxx
-- checking STD_NULLPTR null_ptr.cxx
-- checking STD_REGEX std_regex.cxx
-- Found Git: /usr/bin/git (found version "2.30.0") 
-- [configure-version.h] Creating configure command
-- Making library "maptk"
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success
-- [configure-gui_align] Creating configure command
-- [configure-gui_bundle_adjust] Creating configure command
-- [configure-gui_compute_depth] Creating configure command
-- [configure-gui_default_camera_intrinsics] Creating configure command
-- [configure-gui_filter_tracks] Creating configure command
-- [configure-gui_frame_image_writer] Creating configure command
-- [configure-gui_image_list_reader] Creating configure command
-- [configure-gui_image_video_reader] Creating configure command
-- [configure-gui_initialize] Creating configure command
-- [configure-gui_integrate_depth_maps] Creating configure command
-- [configure-gui_keyframe_image_writer] Creating configure command
-- [configure-gui_mask_list_reader] Creating configure command
-- [configure-gui_mask_video_reader] Creating configure command
-- [configure-gui_st_estimator] Creating configure command
-- [configure-gui_track_features] Creating configure command
-- [configure-gui_triangulate] Creating configure command
-- [configure-track_features_embedded_debug] Creating configure command
-- [configure-log4cplus] Creating configure command
CMake Deprecation Warning at /app/lib/cmake/vtk-9.0/vtk-config.cmake:64 (message):
  The new name for the 'vtkFiltersSources' component is 'FiltersSources'
Call Stack (most recent call first):
  gui/CMakeLists.txt:17 (find_package)

CMake Deprecation Warning at /app/lib/cmake/vtk-9.0/vtk-config.cmake:64 (message):
  The new name for the 'vtkGUISupportQt' component is 'GUISupportQt'
Call Stack (most recent call first):
  gui/CMakeLists.txt:17 (find_package)

CMake Deprecation Warning at /app/lib/cmake/vtk-9.0/vtk-config.cmake:64 (message):
  The new name for the 'vtkIOGeometry' component is 'IOGeometry'
Call Stack (most recent call first):
  gui/CMakeLists.txt:17 (find_package)

CMake Deprecation Warning at /app/lib/cmake/vtk-9.0/vtk-config.cmake:64 (message):
  The new name for the 'vtkIOImage' component is 'IOImage'
Call Stack (most recent call first):
  gui/CMakeLists.txt:17 (find_package)

CMake Deprecation Warning at /app/lib/cmake/vtk-9.0/vtk-config.cmake:64 (message):
  The new name for the 'vtkIOPLY' component is 'IOPLY'
Call Stack (most recent call first):
  gui/CMakeLists.txt:17 (find_package)

CMake Deprecation Warning at /app/lib/cmake/vtk-9.0/vtk-config.cmake:64 (message):
  The new name for the 'vtkIOXML' component is 'IOXML'
Call Stack (most recent call first):
  gui/CMakeLists.txt:17 (find_package)

CMake Deprecation Warning at /app/lib/cmake/vtk-9.0/vtk-config.cmake:64 (message):
  The new name for the 'vtkImagingCore' component is 'ImagingCore'
Call Stack (most recent call first):
  gui/CMakeLists.txt:17 (find_package)

CMake Deprecation Warning at /app/lib/cmake/vtk-9.0/vtk-config.cmake:64 (message):
  The new name for the 'vtkInteractionStyle' component is 'InteractionStyle'
Call Stack (most recent call first):
  gui/CMakeLists.txt:17 (find_package)

CMake Deprecation Warning at /app/lib/cmake/vtk-9.0/vtk-config.cmake:64 (message):
  The new name for the 'vtkInteractionWidgets' component is
  'InteractionWidgets'
Call Stack (most recent call first):
  gui/CMakeLists.txt:17 (find_package)

CMake Deprecation Warning at /app/lib/cmake/vtk-9.0/vtk-config.cmake:64 (message):
  The new name for the 'vtkRenderingAnnotation' component is
  'RenderingAnnotation'
Call Stack (most recent call first):
  gui/CMakeLists.txt:17 (find_package)

CMake Deprecation Warning at /app/lib/cmake/vtk-9.0/vtk-config.cmake:64 (message):
  The new name for the 'vtkRenderingFreeType' component is
  'RenderingFreeType'
Call Stack (most recent call first):
  gui/CMakeLists.txt:17 (find_package)

-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE  
-- Found X11: /usr/include   
-- Looking for XOpenDisplay in /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so
-- Looking for XOpenDisplay in /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so - found
-- Looking for gethostbyname
-- Looking for gethostbyname - found
-- Looking for connect
-- Looking for connect - found
-- Looking for remove
-- Looking for remove - found
-- Looking for shmat
-- Looking for shmat - found
-- Looking for IceConnectionNumber in ICE
-- Looking for IceConnectionNumber in ICE - found
-- Found OpenGL: /usr/lib/x86_64-linux-gnu/libOpenGL.so  found components: OpenGL GLX 
CMake Deprecation Warning at /app/lib/cmake/vtk-9.0/vtk-use-file-deprecated.cmake:1 (message):
  The `VTK_USE_FILE` is no longer used starting with 8.90.
Call Stack (most recent call first):
  gui/CMakeLists.txt:35 (include)

-- File: 'ACKNOWLEDGMENTS'
-- File: 'BUILDINFO'
-- File: 'LICENSE'
-- [configure-telesculptor-config] Creating configure command
-- [configure-telesculptor-install-config] Creating configure command
-- Configuring done
CMake Error at /app/lib/cmake/kwiver/utils/kwiver-utils-targets.cmake:182 (add_executable):
  Target "maptk_detect_and_describe" links to target
  "kwiver::kwiver_algo_core" 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):
  tools/CMakeLists.txt:8 (kwiver_add_executable)

CMake Error at /app/lib/cmake/kwiver/utils/kwiver-utils-targets.cmake:182 (add_executable):
  Target "maptk_track_features" links to target "kwiver::kwiver_algo_core"
  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):
  tools/CMakeLists.txt:17 (kwiver_add_executable)

CMake Error at /app/lib/cmake/kwiver/utils/kwiver-utils-targets.cmake:182 (add_executable):
  Target "maptk_analyze_tracks" links to target "kwiver::kwiver_algo_core"
  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):
  tools/CMakeLists.txt:56 (kwiver_add_executable)

CMake Error at /app/lib/cmake/kwiver/utils/kwiver-utils-targets.cmake:182 (add_executable):
  Target "maptk_match_matrix" links to target "kwiver::kwiver_algo_core" 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):
  tools/CMakeLists.txt:26 (kwiver_add_executable)

CMake Error at /app/lib/cmake/kwiver/utils/kwiver-utils-targets.cmake:182 (add_executable):
  Target "maptk_bundle_adjust_tracks" links to target
  "kwiver::kwiver_algo_core" 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):
  tools/CMakeLists.txt:40 (kwiver_add_executable)

CMake Error at /app/lib/cmake/kwiver/utils/kwiver-utils-targets.cmake:182 (add_executable):
  Target "maptk_apply_gcp" links to target "kwiver::kwiver_algo_core" 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):
  tools/CMakeLists.txt:48 (kwiver_add_executable)

CMake Error at /app/lib/cmake/kwiver/utils/kwiver-utils-targets.cmake:182 (add_executable):
  Target "TeleSculptor" links to target "kwiver::kwiver_adapter" 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):
  gui/CMakeLists.txt:199 (kwiver_add_executable)

CMake Error at /app/lib/cmake/kwiver/utils/kwiver-utils-targets.cmake:182 (add_executable):
  Target "TeleSculptor" links to target "kwiver::kwiver_algo_core" 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):
  gui/CMakeLists.txt:199 (kwiver_add_executable)

CMake Error at /app/lib/cmake/kwiver/utils/kwiver-utils-targets.cmake:182 (add_executable):
  Target "TeleSculptor" links to target "Boost::chrono" 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):
  gui/CMakeLists.txt:199 (kwiver_add_executable)

CMake Error at /app/lib/cmake/kwiver/utils/kwiver-utils-targets.cmake:182 (add_executable):
  Target "TeleSculptor" links to target "Boost::system" 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):
  gui/CMakeLists.txt:199 (kwiver_add_executable)

-- Generating done
CMake Generate step failed.  Build files cannot be regenerated correctly.
Error: module telesculptor: Child process exited with code 1
kevinsmia1939 commented 3 years ago

Hi @mleotta It has been sometime. I hope you are doing well.

It just occurred to me that I can just ship the binary instead of building from source. I package TeleSculptor binary as Flatpak and it works on my machine.

I have to build ICU 60, because most distro use newer version now.

Flatpak run TeleSculptor-1.1.2-Linux-x86_64.sh and automatically answer yes to the license agreement. Any person who install TeleSculptor with Flatpak will not see this agreement.

From what I see, the extracted files does not have License file(?), I will copy the LICENSE from the source instead and put it somewhere manually, where do you want it to be? (/bin /share /lib ...) Would this be acceptable?

TeleSculptor does not have .desktop and .metainfo is that right? If so I will create them.

Do I need to install numpy and pybind11 as well? Or does this binary already bundled them?

Please let me know what you think.

The install command is basically this.

      - chmod +x TeleSculptor-1.1.2-Linux-x86_64.sh
      - yes | ./TeleSculptor-1.1.2-Linux-x86_64.sh
      - cd TeleSculptor-1.1.2-Linux-x86_64 && cp -r {bin,lib,share} /app

Thanks.

kevinsmia1939 commented 3 years ago

Also, will you update Qt soon? I see that it still use 5.11, but it reach the eol already. Edit: NVM, I can see that it is being worked on https://github.com/Kitware/fletch/pull/639

I have some problem. I am not sure what happen, but the directory choose dialog does not work for me. The file chooser dialog popup when I click "New Project". It show "Open" button, but it just open folder, does not choose them, I was unable to choose any folder.

Could this be because TeleSculptor use Qt 5.11?

https://imgur.com/Rdx9gu4

mleotta commented 3 years ago

If installing from binary is acceptable for Flatpak then I have no objections.

Yes, it seems the license file is not installed, so not in the package, we could add it if that is a standard thing to package. I assume it would go under share/telesculptor/[version]. Likewise we don't have .desktop and .metainfo files. I'm not sure what goes in them and where they would get installed. It sounds like we should add them.

We are working on updating Qt to 5.12 as well as various other improvements that will go into TeleSculptor v1.2.0. I'm hoping to get that out soon, but waiting on corresponding Fletch and Kwiver releases.

I'm not sure about that file dialog issue. What OS are you on? We probably need to do more UI testing across different Linux distros.

@borovik135, you've been using the UI on Linux recently. Have you had this issue creating a new project?

kevinsmia1939 commented 3 years ago

If installing from binary is acceptable for Flatpak then I have no objections.

Yes, it seems the license file is not installed, so not in the package, we could add it if that is a standard thing to package. I assume it would go under share/telesculptor/[version]. Likewise we don't have .desktop and .metainfo files. I'm not sure what goes in them and where they would get installed. It sounds like we should add them.

We are working on updating Qt to 5.12 as well as various other improvements that will go into TeleSculptor v1.2.0. I'm hoping to get that out soon, but waiting on corresponding Fletch and Kwiver releases.

I'm not sure about that file dialog issue. What OS are you on? We probably need to do more UI testing across different Linux distros.

@borovik135, you've been using the UI on Linux recently. Have you had this issue creating a new project?

Thanks for reply, I create .desktop and metainfo.xml file already, I will be submitting it to you soon.

I use openSUSE Tumbleweed KDE. About the UI thing. My guess is that the upstream binary use Qt 5.11. But when using binary inside Flatpak, it use portal to Qt 5.15, which might cause some compatibility issue.

I think I will just wait until TeleSculptor update to Qt 5.12, and use KDE Sdk 5.12 so it would be easier to figured out.

https://imgur.com/HMJcHkd

skinkie commented 3 years ago

When trying to build TeleSculptor without Fletch I am able to get up to this point, where I am missing kwiver::kwiver_adapter, kwiver::kwiver_algo_qt_widgets. I am quite sure Boost contains everything it should because Kwiver detects it. Any suggestions what might me missing?

CMake Error at /usr/local/lib/cmake/kwiver/utils/kwiver-utils-targets.cmake:182 (add_executable):
  Target "TeleSculptor" links to target "kwiver::kwiver_adapter" 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):
  gui/CMakeLists.txt:150 (kwiver_add_executable)

CMake Error at /usr/local/lib/cmake/kwiver/utils/kwiver-utils-targets.cmake:182 (add_executable):
  Target "TeleSculptor" links to target "kwiver::kwiver_algo_qt_widgets" 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):
  gui/CMakeLists.txt:150 (kwiver_add_executable)

CMake Error at /usr/local/lib/cmake/kwiver/utils/kwiver-utils-targets.cmake:182 (add_executable):
  Target "TeleSculptor" links to target "Boost::chrono" 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):
  gui/CMakeLists.txt:150 (kwiver_add_executable)

CMake Error at /usr/local/lib/cmake/kwiver/utils/kwiver-utils-targets.cmake:182 (add_executable):
  Target "TeleSculptor" links to target "Boost::system" 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):
  gui/CMakeLists.txt:150 (kwiver_add_executable)

CMake Error at /usr/local/lib/cmake/kwiver/utils/kwiver-utils-targets.cmake:182 (add_executable):
  Target "TeleSculptor" links to target "kwiver::kwiver_algo_vtk" 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):
  gui/CMakeLists.txt:150 (kwiver_add_executable)
cmake .. -DCMAKE_BUILD_TYPE:STRING=Release -DKWIVER_ENABLE_SPROKIT=ON -DKWIVER_ENABLE_C_BINDINGS=ON -DKWIVER_ENABLE_TOOLS=ON -DKWIVER_ENABLE_PYTHON=OFF -DKWIVER_ENABLE_ARROWS=ON
-- Current path: '/home/skinkie/Sources/kwiver/CMake'
-- Import CMake future from '/home/skinkie/Sources/kwiver/CMake/future'
-- Import CMake future '3.10'
-- Performing Test has_compiler_flag--Werror=return-type
-- Performing Test has_compiler_flag--Werror=return-type - Success
-- Performing Test has_compiler_flag--Werror=non-virtual-dtor
-- Performing Test has_compiler_flag--Werror=non-virtual-dtor - Success
-- Performing Test has_compiler_flag--Werror=narrowing
-- Performing Test has_compiler_flag--Werror=narrowing - Success
-- Performing Test has_compiler_flag--Werror=init-self
-- Performing Test has_compiler_flag--Werror=init-self - Success
-- Performing Test has_compiler_flag--Werror=reorder
-- Performing Test has_compiler_flag--Werror=reorder - Success
-- Performing Test has_compiler_flag--Werror=overloaded-virtual
-- Performing Test has_compiler_flag--Werror=overloaded-virtual - Success
-- Performing Test has_compiler_flag--Werror=cast-qual
-- Performing Test has_compiler_flag--Werror=cast-qual - Success
-- Performing Test has_compiler_flag--Werror=vla
-- Performing Test has_compiler_flag--Werror=vla - Success
-- Performing Test has_compiler_flag--Wshadow=local
-- Performing Test has_compiler_flag--Wshadow=local - Success
-- checking CPP_AUTO auto.cxx
-- checking CPP_CONSTEXPR constexpr.cxx
-- checking CPP_DEFAULT_CTOR default-ctor.cxx
-- checking CPP_FINAL final.cxx
-- checking CPP_NOEXCEPT throw-noexcept.cxx
-- checking CPP_RANGE_FOR range-for.cxx
-- checking STD_CHRONO std_chrono.cxx
-- checking STD_NULLPTR null_ptr.cxx
-- checking STD_REGEX std_regex.cxx
-- Making library "kwiver_algo_core"
-- Building plugin "kwiver_algo_core"
-- Making library "kwiver_algo_core_plugin"
-- Making library "kwiver_algo_core_applets"
-- Making library "kwiver_algo_mvg"
-- Building plugin "kwiver_algo_mvg"
-- Making library "kwiver_algo_mvg_plugin"
-- Making library "kwiver_algo_mvg_applets"
-- Making library "kwiver_algo_klv"
-- Making library "sprokit_pipeline"
-- Making library "sprokit_pipeline_util"
-- Making library "sprokit_applets"
-- Making library "processes_clusters"
-- Making library "processes_examples"
-- Making library "schedulers"
-- Making library "schedulers_examples"
CMake Deprecation Warning at vital/kwiversys/CMakeLists.txt:78 (CMAKE_MINIMUM_REQUIRED):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- Making library "vital"
-- Making library "vital_exceptions"
-- Making library "vital_algo"
-- Making library "algo_explorer_plugin"
-- Making library "vital_util"
-- Making library "vital_c"
-- Making library "vital_config"
-- Making library "format_config"
-- Making library "vital_logger"
-- Making library "vital_vpm"
-- Making library "kwiver_tools_applet"
-- Making library "vital_applets"
-- Making library "explorer_plugin"
-- [configure-ceres_bundle_adjuster] Creating configure command
-- [configure-core_feature_descriptor_io] Creating configure command
-- [configure-core_feature_tracker] Creating configure command
-- [configure-core_fmatrix_guided_feature_matcher] Creating configure command
-- [configure-core_homography_guided_feature_matcher] Creating configure command
-- [configure-core_image_list_video_input] Creating configure command
-- [configure-core_nonmax_detector] Creating configure command
-- [configure-core_output_homography_generator] Creating configure command
-- [configure-core_pca_canonical_tfm] Creating configure command
-- [configure-core_track_filter] Creating configure command
-- [configure-core_video_input_image_list] Creating configure command
-- [configure-core_video_input_image_pos_list] Creating configure command
-- [configure-cuda_integrate_depth_maps] Creating configure command
-- [configure-default_camera_intrinsics] Creating configure command
-- [configure-ffmpeg_video_input] Creating configure command
-- [configure-loop_closer_bad_frames] Creating configure command
-- [configure-loop_closer_homography] Creating configure command
-- [configure-loop_closer_keyframe] Creating configure command
-- [configure-loop_closer_multi_method] Creating configure command
-- [configure-mvg_hierarchical_bundle_adjuster] Creating configure command
-- [configure-mvg_initialize_cameras_landmarks] Creating configure command
-- [configure-mvg_initialize_cameras_landmarks_basic] Creating configure command
-- [configure-ocv_klt_tracker] Creating configure command
-- [configure-ocv_ORB_detector_descriptor] Creating configure command
-- [configure-ocv_SURF_detector_descriptor] Creating configure command
-- [configure-super3d_depth_map] Creating configure command
-- [configure-applet-dump_klv] Creating configure command
-- [configure-applet-estimate_depth] Creating configure command
-- [configure-applet-fuse_depth] Creating configure command
-- [configure-applet-init_cameras_landmarks] Creating configure command
-- [configure-applet-track_features] Creating configure command
-- [configure-applet-color_mesh] Creating configure command
-- [configure-models-default_burnout_600_iters] Creating configure command
-- [configure-pipelines-detect_burnin] Creating configure command
-- [configure-pipelines-inpaint_burnin] Creating configure command
-- [configure-version.h] Creating configure command
-- Configuring done
-- Generating done
-- Build files have been written to: /home/skinkie/Sources/kwiver/build
kevinsmia1939 commented 3 years ago

Hi, I'm here to report that the new TeleSculptor works now, I can choose the folder properly now. I will update the Flatpak for testing soon.

kevinsmia1939 commented 3 years ago

I submit pr to flathub here, waiting to be build and test. https://github.com/flathub/flathub/pull/2525

kevinsmia1939 commented 3 years ago

@mleotta Hi, Does TeleSculptor need network connection? I create .desktop and metainfo.xml file for TeleSculptor, I want to submit this patch, which directory where do you want it to?

mleotta commented 3 years ago

@kevinsmia1939 I would suggest putting those files in packaging since that is where we have been putting file that are need to support packaging TeleSculptor. TeleSculptor does not need a network connect after it is built and installed.

kevinsmia1939 commented 3 years ago

I create TeleSculptor Flatpak!

This is a test repo, but it can be install like this.

  1. Install Flatpak, sudo apt install flatpak
  2. flatpak install --user https://dl.flathub.org/build-repo/58812/org.telesculptor.TeleSculptor.flatpakref
  3. There should be TeleSculptor icon in the menu.
kevinsmia1939 commented 3 years ago

I guess this can be close now. It is here: https://flathub.org/apps/details/org.telesculptor.TeleSculptor