Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
VTK
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Michael Migliore
VTK
Commits
cc20328b
Unverified
Commit
cc20328b
authored
1 year ago
by
Jean-Christophe Fillion-Robin
Browse files
Options
Downloads
Patches
Plain Diff
docs: Update build instructions based on "build_windows_vs.md" document
parent
d0360fc1
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
Documentation/dev/build.md
+150
-50
150 additions, 50 deletions
Documentation/dev/build.md
Documentation/docs/modules/index.md
+2
-1
2 additions, 1 deletion
Documentation/docs/modules/index.md
with
152 additions
and
51 deletions
Documentation/dev/build.md
+
150
−
50
View file @
cc20328b
...
...
@@ -18,14 +18,36 @@ Makefiles, and Visual Studio generators are the most well-tested however.
Note that VTK does not support in-source builds, so you must have a build tree
that is not the source tree.
## Obtaining the source
## Obtaining the source
s
To obtain VTK's sources locally, clone this repository using
[
Git
][
git
]
.
There are two approaches:
::::{tab-set}
:::{tab-item} Release Download
1.
Download the source release
`VTK-X.Y.Z.tar.gz`
from https://vtk.org/download/.
2.
Create a folder for VTK.
3.
Extract the contents of the VTK folder in the downloaded archive to the subfolder called
`source`
:::
:::{tab-item} Git Clone
To obtain VTK's sources locally, clone the VTK repository using
[
Git
][
git
]
.
[
git
]:
https://git-scm.org
Open
`Git Bash`
on Windows or a terminal on Linux and macOS and
execute the following:
```
sh
git clone
--recursive
https://gitlab.kitware.com/vtk/vtk.git
mkdir
-p
~/vtk
git clone
--recursive
https://gitlab.kitware.com/vtk/vtk.git ~/vtk/source
```
:::
::::
To use the latest features being developed or to make changes and
contribute to VTK, download the source using
**Git Clone**
.
## Prerequisites
...
...
@@ -40,11 +62,6 @@ Required:
If the system package management utilities do not offer cmake or if the offered version is too old
Precompiled binaries available on
[
CMake's download page
][
cmake-download
]
.
```{tip}
If you are using cmake through the system's package management it is highly recommended install
`ccmake` (package `cmake-curses-gui` on Ubuntu/Debian) that allows to interactively set building options.
```
*
Supported compiler
-
GCC 4.8 or newer
-
Clang 3.3 or newer
...
...
@@ -89,86 +106,169 @@ Required:
likely necessary for bug fixes and support. Its source and build instructions
can be found on
[
its website
][
mesa
]
.
[
cmake
]:
https://cmake.org
[
cmake-download
]:
https://cmake.org/download
[
ffmpeg
]:
https://ffmpeg.org
[
mpi
]:
https://www.mcs.anl.gov/research/projects/mpi
[
mpich
]:
https://www.mpich.org
[
msmpi
]:
https://docs.microsoft.com/en-us/message-passing-interface/microsoft-mpi
[
openmpi
]:
https://www.open-mpi.org
[
python
]:
https://python.org
[
qt-download
]:
https://download.qt.io/official_releases/qt
[
mesa
]:
https://www.mesa3d.org
## Creating the Build Environment
### Linux (Ubuntu/Debian)
::::{tab-set}
:::{tab-item} Windows
*
Install CMake
*
Install
[
Visual Studio Community Edition
][
visual-studio
]
Install the following packages:
*
During installation select the "desktop development with C++" workload.
*
Use "x64 Native Tools Command Prompt" for the installed Visual Studio
version to configure with CMake and to build with ninja.
*
Get
[
ninja
][
ninja
]
. Unzip the binary and put it in
`PATH`
. Note that newer
Visual Studio releases come with a version of
`ninja`
already and should
already exist in
`PATH`
within the command prompt.
[
ninja
]:
https://ninja-build.org
[
visual-studio
]:
https://visualstudio.microsoft.com/vs
:::
:::{tab-item} Linux (Ubuntu/Debian)
Install the following packages:
```
bash
$
sudo
apt
install
\
build-essential
\
cmake
\
cmake-curses-gui
\
mesa-common-dev
\
mesa-utils
\
freeglut3-dev
\
ninja-build
```
:::
```
{tip}
`ninja` is a speedy replacement for `make`, highly recommended.
```
:::{tab-item} macOS
### Windows
*
Install CMake
*
[
Visual Studio Community Edition
][
visual-studio
]
*
Install XCode
*
Use "x64 Native Tools Command Prompt" for the installed Visual Studio
version to configure with CMake and to build with ninja.
*
Ensure XCode command line tools are installed:
*
Get
[
ninja
][
ninja
]
. Unzip the binary and put it in
`PATH`
. Note that newer
Visual Studio releases come with a version of
`ninja`
already and should
already exist in
`PATH`
within the command prompt.
```
bash
xcode-select
--install
```
:::
## Configure and Building
::::
```
{note}
`ninja` is a more efficient alternative to `Makefiles` or Visual Studio solution files. The
speed increase is the most noticeable when doing incremental build.
```
## Configure
In order to build, CMake requires two steps, configure and build. VTK itself
does not support what are known as in-source builds, so the first step is to
create a build directory.
::::{tab-set}
:::{tab-item} Windows (Ninja)
Open "x64 Native Tools Command Prompt" for the installed Visual Studio:
```
sh
mkdir
-p
vtk/build
cd
vtk/build
ccmake
-GNinja
../path/to/vtk/source
# -GNinja may be skipped to use the default generator for each platform
ccmake
-GNinja
-S
%HOMEPATH%
\v
tk
\s
ource
-B
%HOMEPATH%
\v
tk
\b
uild
```
CMake's GUI has input entries for the build directory and the generator
already. Note that on Windows, the GUI must be launched from a "Native Tools
Command Prompt" available with Visual Studio in the start menu.
Note that CMake GUI must also be launched from the "Native Tools Command Prompt".
:::
:::{tab-item} Windows (Visual Studio)
Use CMake to generate a Visual Studio solution file (
`.sln`
).
1.
Open CMake GUI, either by typing
`cmake-gui`
on the command prompt or from the start-menu.
2.
Enter the source and build directories
3.
Click
`[Configure]`
4.
You will now get a selection screen in which you can specify your "generator". Select the one you need.
5.
We are now presented with a few options that can be turned on or off as desired.
6.
Click
`[Configure]`
to apply the changes.
7.
Click
`[Generate]`
. This will populate the "build" sub-folder.
8.
Finally, click
`[Open Project]`
to open the generated solution in Visual Studio.
:::
:::{tab-item} Linux/macOS
```
sh
mkdir
-p
~/vtk/build
cd
~/vtk/build
ccmake
-GNinja
../path/to/vtk/source
```
The parameter
`-GNinja`
may be skipped to use the default generator (e.g
`Unix Makefiles`
).
:::
::::
```
{admonition} **Missing dependencies**
:class: warning
CMake may not find all dependencies automatically in all cases. The steps
needed to find any given package depends on the package itself. For general
assistance, please see the documentation for
needed to find any given package depends on the package itself.
For general assistance, please see the documentation for
[`find_package`'s search procedure][cmake-find_package-search] and
[the relevant Find module][cmake-modules-find] (as available).
[cmake-find_package-search]: https://cmake.org/cmake/help/latest/command/find_package.html#search-procedure
[cmake-modules-find]: https://cmake.org/cmake/help/latest/manual/cmake-modules.7.html#find-modules
```
:::{hint}
Different features can be enabled/disabled by setting the
[
Build Settings
](
build_settings.md
)
during the configure stage.
:::
## Building
To build VTK:
::::{tab-set}
To build vtk run:
:::{tab-item} Windows (Ninja)
```
sh
cmake
--build
.
cmake
--build
%HOMEPATH%
\v
tk
\b
uild
--config
Release
```
:::
```
{tip}
Different features can be enabled/disabled by setting the [Build Settings](build_settings.md) during the configure stage.
:::{tab-item} Windows (Visual Studio)
Open the generated solution file.
1.
Set the configuration to "Release"
2.
On the menu bar, choose
`Build`
, and then choose
`Build Solution`
.
:::
:::{tab-item} Linux/macOS
```
sh
cmake
--build
~/vtk/build
```
:::
[
cmake
]:
https://cmake.org
[
cmake-download
]:
https://cmake.org/download
[
cmake-find_package-search
]:
https://cmake.org/cmake/help/latest/command/find_package.html#search-procedure
[
cmake-modules-find
]:
https://cmake.org/cmake/help/latest/manual/cmake-modules.7.html#find-modules
[
ffmpeg
]:
https://ffmpeg.org
[
git
]:
https://git-scm.org
[
mesa
]:
https://www.mesa3d.org
[
mpi
]:
https://www.mcs.anl.gov/research/projects/mpi
[
mpich
]:
https://www.mpich.org
[
msmpi
]:
https://docs.microsoft.com/en-us/message-passing-interface/microsoft-mpi
[
ninja
]:
https://ninja-build.org
[
openmpi
]:
https://www.open-mpi.org
[
python
]:
https://python.org
[
qt
]:
https://qt.io
[
qt-download
]:
https://download.qt.io/official_releases/qt
[
visual-studio
]:
https://visualstudio.microsoft.com/vs
::::
This diff is collapsed.
Click to expand it.
Documentation/docs/modules/index.md
+
2
−
1
View file @
cc20328b
...
...
@@ -22,7 +22,8 @@ cmake -DVTK_MODULE_ENABLE_<module name>=WANT ...
```
during the
[
configuration
](
../build_instructions/index.md#configure-and-building
)
stage.
[
configuration
](
../build_instructions/index.md#configure
)
stage.
Disabling a module can be done as follows:
```
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment