Difference between revisions of "Documentation/4.0/Developers/Tutorials/QtCreator"

From SlicerWiki
Jump to: navigation, search
(Created page with '= Qt Creator = [http://qt.nokia.com/products/developer-tools?currentflipperobject=821c7594d32e33932297b1e065a976b8 Qt Creator] is a cross-platform IDE that fully integrates Qt in…')
 
Line 11: Line 11:
  
 
* Open /path/to/Slicer-src/CMakeLists.txt in qtcreator, when prompted, choose the build directory where Slicer was configured and compiled in the previous step. (/path/to/Slicer-Superbuild/Slicer-build)
 
* Open /path/to/Slicer-src/CMakeLists.txt in qtcreator, when prompted, choose the build directory where Slicer was configured and compiled in the previous step. (/path/to/Slicer-Superbuild/Slicer-build)
 +
** '''NOTE:''' You can select either the binary tree of the SuperBuild or the binary tree of the Slicer-build that is inside the binary tree of the SuperBuild.  The former allows you to build all of the packages that Slicer depends on and build Slicer itself.  The latter provides a better IDE experience when working on Slicer itself (recognizing types, pulling up documentation, cross-referencing the code, ...).

Revision as of 14:43, 28 March 2011

Home < Documentation < 4.0 < Developers < Tutorials < QtCreator

Qt Creator

Qt Creator is a cross-platform IDE that fully integrates Qt into the development of applications. Slicer CMake project is supported by Qt Creator, the following describes tips using Qt Creator.

  • Configure and compile Slicer outside qtcreator first, from command line (more information here .
  • After Slicer has been compiled successfully, turn off verbose make using this from Slicer-build:
cmake -D CMAKE_VERBOSE_MAKEFILE:BOOL=OFF .
  • Launch qtcreator through slicer to setup paths and paths to paths (this allows qtcreator to locate our custom designer plugins):
Slicer4 --launch /path/to/qtcreator
  • Open /path/to/Slicer-src/CMakeLists.txt in qtcreator, when prompted, choose the build directory where Slicer was configured and compiled in the previous step. (/path/to/Slicer-Superbuild/Slicer-build)
    • NOTE: You can select either the binary tree of the SuperBuild or the binary tree of the Slicer-build that is inside the binary tree of the SuperBuild. The former allows you to build all of the packages that Slicer depends on and build Slicer itself. The latter provides a better IDE experience when working on Slicer itself (recognizing types, pulling up documentation, cross-referencing the code, ...).