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

From Slicer Wiki
Jump to: navigation, search
Line 1: Line 1:
 
= Qt Creator =
 
= Qt Creator =
[http://qt.nokia.com/products/developer-tools?currentflipperobject=821c7594d32e33932297b1e065a976b8 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.  
+
[http://qt.nokia.com/products/developer-tools?currentflipperobject=821c7594d32e33932297b1e065a976b8 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 items aim at describing how it could be used.  
  
* Configure and compile Slicer outside qtcreator first, from command line (more information [[Slicer4:Build_Instructions|here]] .
+
* Configure and compile Slicer outside qtcreator first. (ie.e on linux from command line). More details regarding the build process are available (more information [[Slicer4:Build_Instructions|here]] .
  
 
* After Slicer has been compiled successfully, turn off verbose make using this from Slicer-build:
 
* After Slicer has been compiled successfully, turn off verbose make using this from Slicer-build:
Line 9: Line 9:
 
* Launch qtcreator through slicer to setup paths and paths to paths (this allows qtcreator to locate our custom designer plugins):
 
* 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
 
  Slicer4 --launch /path/to/qtcreator
 +
 +
* You can also start QtDesigner the same way (Slicer4 --launch /path/to/designer). It could be useful to have an instance of QtDesigner and an instance of QtCreator open simultaneously while designing and implementing user interface.
  
 
* 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 all from within Qt Creator.  The latter provides a better IDE experience when working on Slicer itself (recognizing types, pulling up documentation, cross-referencing the code, ...).
 
** '''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 all from within Qt Creator.  The latter provides a better IDE experience when working on Slicer itself (recognizing types, pulling up documentation, cross-referencing the code, ...).

Revision as of 22:51, 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 items aim at describing how it could be used.

  • Configure and compile Slicer outside qtcreator first. (ie.e on linux from command line). More details regarding the build process are available (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
  • You can also start QtDesigner the same way (Slicer4 --launch /path/to/designer). It could be useful to have an instance of QtDesigner and an instance of QtCreator open simultaneously while designing and implementing user interface.
  • 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 all from within Qt Creator. The latter provides a better IDE experience when working on Slicer itself (recognizing types, pulling up documentation, cross-referencing the code, ...).