Commit 790255be authored by Nick Laurenson's avatar Nick Laurenson
Browse files

Restore Superbuild and create a lidarview-common-superbuild

parent f49662d6
cmake_minimum_required(VERSION 2.8.8)
project(LidarViewSuperBuild)
#-----------------------------------------------------------------------------
# All the function and variable bellow are here because we rely on lidarview's
# superbuild.
# To see which function/variable cana/needs to be set, please take a look at
# the CMakeLists.txt inside "lidarview-common-superbuild"
#-----------------------------------------------------------------------------
# Setup CMAKE_MODULE_PATH so that platform specific configurations are processed
# before the generic ones.
set (CMAKE_MODULE_PATH
"${CMAKE_CURRENT_SOURCE_DIR}/Projects"
${CMAKE_MODULE_PATH})
function (add_project_to_superbuild var)
# list cannot append to parent's scope so we do it in two steps
list(APPEND "${var}" lidarview)
set("${var}" "${${var}}" PARENT_SCOPE)
endfunction ()
list(APPEND superbuild_version_files
"${CMAKE_CURRENT_LIST_DIR}/versions.cmake")
add_subdirectory(lidarview-common-superbuild/)
......@@ -78,7 +78,6 @@ function (superbuild_find_projects var)
python
pythonqt
qt5
lidarview
zlib
ceres
glog
......@@ -103,6 +102,7 @@ function (superbuild_find_projects var)
endif()
endif()
add_project_to_superbuild(projects)
set("${var}"
${projects}
PARENT_SCOPE)
......
# LidarView-Superbuild
LidarView-Superbuild is a project to build LidarView or any other LidarView-based application (VeloView, OusterView, ...) and its dependencies.
The project is a small wrapper above Paraview-Superbuild, and provide the common dependencies needed by all viewer and some extra ones.
## How to use the Superbuild
To use the superbuild, simply include this project into your Viewer as a submodule. We recommand you to use this architecture as it is similar to paraview's one.
# customviewer repository
├── Superbuild
│ ├── lidarview-common-superbuild # the common-superbuild
│ ├── Projects # how to compile the projects
│ │ └──customviewer.cmake
│ ├── CMakeLists.txt
│ └── versions.cmake # how to get the project source code
├── ...
├── Application
├── LICENSE
└── README.md
The CMakeLists.txt must define some function/variable to overight the common build default behaviour. Here is a minimalist example:
```cmake
set (CMAKE_MODULE_PATH
"${CMAKE_CURRENT_SOURCE_DIR}/Projects"
${CMAKE_MODULE_PATH})
function (add_project_to_superbuild var)
# list cannot append to parent's scope so we do it in two steps
list(APPEND "${var}" customviewer)
set("${var}" "${${var}}" PARENT_SCOPE)
endfunction ()
list(APPEND superbuild_version_files
"${CMAKE_CURRENT_LIST_DIR}/versions.cmake")
add_subdirectory(lidarview-common-superbuild)
```
......@@ -19,10 +19,6 @@ superbuild_set_revision(paraview
GIT_REPOSITORY https://gitlab.kitware.com/bjacquet/paraview.git
GIT_TAG origin/5.4CustomForLidarView)
superbuild_set_revision(lidarview
SOURCE_DIR ${CMAKE_SOURCE_DIR}/..
DOWNLOAD_COMMAND "")
if (WIN32)
superbuild_set_revision(pcap
GIT_REPOSITORY http://github.com/patmarion/winpcap.git
......
superbuild_set_revision(lidarview
SOURCE_DIR ${CMAKE_SOURCE_DIR}/..
DOWNLOAD_COMMAND "")
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment