FS3D
|
The build process is divided into three steps:
This page uses the following convention: all libraries are installed in %ROOT_DIR%, under their own folder. They are built in a dedicated directory named "build"
In order to build fs3d from sources, a few tools are required:
in order to build the documentation (both user and developper):
in order to build the python selection plugin:
Additionaly, on linux, graphic card with proprietary drivers are strongly recommanded.
At the moment, no package is provided. Thus, compiling/running FS3D_cpp require the following packages:
Some provides auto-extracting archive, in which case, the process is quite straightforward. Others have to be build from sources (all have cmake support) in which case the process is as follow:
The installer is a self executable archive.
dtk has itself a dependency on Qt, so it has to be built after Qt was installed. Hereinafter, %QT_DIR% is the folder in which Qt is installed (for example /opt/Qt/5.6/gcc_64/lib/cmake
this may be achieved by the following script:
VTK has itself a dependency on Qt, so it has to be built after Qt was installed. Hereinafter, %QT_DIR% is the folder in which Qt is installed (for example /opt/Qt/5.6/gcc_64/lib/cmake
this may be achieved by the following script:
FLENS is header-only, hence it does not need to be built.
this may be achieved by the following script:
dtkLinearDenseAlgebra has itself a dependency on Qt and on dtk, so it has to be built after Qt and dtk were installed. Hereinafter, %QT_DIR% is the folder in which Qt is installed (for example /opt/Qt/5.6/gcc_64/lib/cmake) and %dtk_DIR% is the folder in which dtk is installed (for example /opt/dtk/build)
this may be achieved by the following script:
The installer is a self executable archive.
With the correct permissions and the environment described above, installing fs3d comes down to one more cmake-based build.
this may be achieved by the following script:
In order to make Fs3d find its libraries, the MCR must be added to the library path:
export LD_LIBRARY_PATH="%MCR_PATH%/v80/bin/glnxa64"
The recommended way is to use a launcher script like the one below:
update VTK to 6.3, and activate OpenGl2 rendering, and vtkQtGuiSupport in the advanced options
edit the file dtk.conf in ~/.config/inria and add a section:
This is caused by a corrupted file remaining from an older failed build. Clean the build directory and restarting a clean build usually solve the issue: