Developer FAQ: Building | 开发人员常遇到的问题：构建

1.How is organized the Slicer build tree （3D slicer 组织架构）?

The Slicer build tree has two levels:
~/Projects/Slicer-SuperBuild
~/Projects/Slicer-SuperBuild/Slicer-build
The first level manages all the external dependencies（外部依赖关系）of Slicer (VTK, ITK, Python, ...). The second level is the"traditional"build directory of Slicer.

Slicer directory structure as followed:

Build Tree & Install Tree:

                                                 

           Build tree                                                            Install tree

The X and Y in Slicer-X.Y respectively stand for Slicer_MAJOR_VERSION and Slicer_MINOR_VERSION

Extension install and build tree:

Extensions installation path can be specified in the Extension settings.

API:

vtkSlicerApplicationLogic  provides some convenient functions allowing to obtain the share directory associated with a given module filepath.
Note also that if vtkSlicerConfigure is included the macros (宏)Slicer_CLIMODULES_SUBDIR, Slicer_QTLOADABLEMODULES_SUBDIR  and   Slicer_QTSCRIPTEDMODULES_SUBDIR will be available.
Application settings (including the search path for modules/extensions) are stored ina .ini file. The location of the file depends on the OS:
Linux + Mac OS X: ~/.config/www.na-mic.org/Slicer.ini
Windows: C:\Users\USERNAME\AppData\Roaming\NA-MIC\Slicer.ini。

2.What is a clean build？

Doing a clean build means that
(1) all directories and files in the top-level build directory ~/Projects/Slicer-SuperBuild are removed.
and
(2) you updated your source checkout and have no locally modified files.

3.What to do if QtSDK installer hangs （安装程序挂起）?

If QtSDK installer hangs, use -style cleanlooks command line option（利用命令行选项）. 

4.Which minimum version of GLIBC（函数库的最低版本） is needed to build Slicer ?

The minimum version of GLIBC required to build Slicer is defined by the minimum version required by thepre-compiler binaries used when building Slicer.

5.What to do if Visual Studio compiler crashes （VS编译器崩溃）?

If the compiler crashes on Windows saying "Microsoft C/C++ Compiler Driver has stopped working", then it's most probably due to long build folder paths. To fix this the Slicer build directory should be moved and/or renamed. A typical build folder path is C:\S4D

如果Windows上的C++编译器提醒“Microsoft C/C++ Compiler Driver has stopped working”，这很有可能是因为我们的文件路径名设置太长导致的。更改Slicer组件目录或者清除目录可以解决这个问题。一个典型的文件目录就是：C:\S4D