1. 30 Mar, 2021 1 commit
  2. 23 Mar, 2021 1 commit
  3. 19 Feb, 2021 6 commits
  4. 26 Jan, 2021 7 commits
  5. 25 Jan, 2021 6 commits
  6. 28 Sep, 2020 1 commit
  7. 08 Sep, 2020 1 commit
    • Nicolas Cadart's avatar
      Restore Boost_LIBRARY_DIR* variables in PCL CMake configuration · 632e3fc0
      Nicolas Cadart authored
      These variables should not be necessary, as BOOST_LIBRARYDIR is properly set.
      It works as is on MacOS and Windows.
      For some reason, on Linux, PCL still finds and uses the system Boost, ignoring these variables.
      Boost_LIBRARY_DIR_DEBUG and Boost_LIBRARY_DIR_Release variables should be filled by CMake according to the BOOST_LIBRARYDIR hint.
      By directly setting these variables, we ensure using the correct superbuild Boost libs.
  8. 07 Sep, 2020 2 commits
  9. 28 Aug, 2020 3 commits
    • Nicolas Cadart's avatar
      Merge branch 'fix/CheckSystemBoostEnvVar' into 'master' · 4a99c6b0
      Nicolas Cadart authored
      Check system boost environment variables and clean boost related CMake variables
      See merge request !18
    • Nicolas Cadart's avatar
      Remove useless Boost related lines in pcl.cmake · 7b70763c
      Nicolas Cadart authored
      Removes Boost_USE_STATIC which does not exist in CMake > 3.0.
      Removes Boost_LIBRARY_DIR_DEBUG/RELEASE which are automatically set by FindBoost.cmake according to BOOST_LIBRARYDIR hint.
    • Nicolas Cadart's avatar
      Check for Boost environment variables hiding superbuild Boost install · ee4a2a9e
      Nicolas Cadart authored
      If some Boost environment variables are defined, they could hide the
      superbuild Boost install.
      This can lead to superbuild failure if the system boost does not have
      all required components.
      It may also lead to runtime errors if all binaries were not built using
      the same boost libs (system VS superbuild ones).
      This commit add a check to verify the definition of these environment
      variables if user does not want to use his system boost install.
  10. 13 Aug, 2020 2 commits
  11. 13 Jul, 2020 3 commits
  12. 07 Jul, 2020 2 commits
  13. 17 Jun, 2020 1 commit
  14. 12 Jun, 2020 2 commits
  15. 11 Jun, 2020 1 commit
    • Nicolas Cadart's avatar
      Enable Paraview embedded documentation · 18174f02
      Nicolas Cadart authored
      This option was set twice in Paraview superbuild project, once at ON, the second at OFF, overriding the first.
      This commit removes the second setting, enabling back the option.
      If set to ON, plugins documentation is auto-generated from proxy XML files.
      This doc becomes available in LidarView Online Help, and can be accessed via the "?" help button of each entry in the Pipeline Browser.
      Note that this option has nothing to do with code API documentation generation, and doxygen is not triggered via this command.
  16. 27 May, 2020 1 commit