/**
\page HowToNewProject Creating a new MITK project

\tableofcontents

This page is intended to give a comprehensive guide to setting up your own MITK based
project. It will use the application framework provided by MITK and is probably the
preferred way for most users.

The first part of this document is a tutorial aimed at newcomers to MITK and possibly
%CMake and tries to give as much help as possible on setting up your own project. If
you are looking for more technical information about customizing MITK, the structure
of the superbuild or packaging you might want to read the
\ref HowToNewProjectAdvancedInformation.

If you have set up your MITK project already and want to start developing you could
take a look at \ref TutorialPage.

\section HowToNewProjectGettingStarted Getting Started

Use the <a href="https://github.com/MITK/MITK-ProjectTemplate">MITK project template</a> as an
example-based project template.

\section HowToNewProjectPrerequisites Prerequisites

What ever option you choose, a MITK-based project needs essentially the same
prerequisites as MITK itself. Please see \ref BuildInstructions_Prerequisites for
details.
\note If you use one of the two options above you will \b not \b need to build MITK
yourself. This will be done automatically.

\section HowToNewProjectCreatingSourceDir Preparing your source directory

In order to start developing with MITK, you first have to set up the source directory
for your project.

\subsection HowToNewProjectSourceUsingTemplate Using the MITK Project Template

Download the project as a tarball or zipball and extract it to your desired source
directory.

\note This is a <b>template</b>. You must modify it such that it fits the needs of
your particular project. Especially you should do a global search and replace for
the string "awesome" to rename the template application and plug-in. You may want
to rename some files too.

\section HowToNewProjectGeneratingCMake Generating your binary with CMake

After you have set up your source directory you can proceed to generate your binary
directory using %CMake. Depending on your operating system and preferences you might
want to use "cmake-gui" or "ccmake" (shell). This document assumes you are using
cmake-gui.

<ol>
 <li> Start "cmake-gui" and enter your source (e.g. "D:/AwesomeProject") and binary
      directory (e.g. "D:/AwesomeProject-superbuild").
 <li> Upon first pressing "Configure" you will be prompted to select your generator.
      This determines what project files will be generated by %CMake. Set this to the
      development tool you are intending to use (e.g. "Visual Studio 2010 64Bit" or
      "linux makefiles".
 <li> Press "Configure" until no new variables appear and then "Generate". Now all
      project files have been generated into your binary directory.
 <li> Double-check that the right Qt version is used.
</ol>

Now you are ready to compile your code. Depending on your choice of tool this will
be done differently, we cover two possibilities here.

\subsection HowToNewProjectCompilingLinuxMakefiles Compiling using linux makefiles

<ol>
 <li> In the shell, switch to your binary directory.
 <li> type "make" and hit enter
</ol>

\subsection HowToNewProjectCompilingVisualStudio Compiling using visual studio

We assume your application is called "AwesomeApp" and your project "AwesomeProject"
and your binary directory is "D:/AwesomeProject-superbuild/". Replace names and
paths accordingly.

<ol>
 <li> Close %CMake and open "D:/AwesomeProject-superbuild/AwesomeProject-superbuild.sln".
      Your Visual Studio should appear and by pressing F7 you start the compilation.
      This will clone the MITK source code, build it, and then start building your own
      project.
 <li> After the superbuild compilation has finished, close the superbuild solution file and start
      the build solution file "D:/AwesomeProject-superbuild/AwesomeProject-build/AwesomeProject.sln"
 <li> Set the "AwesomeApp" project as start-up project (right click > "Set as StartUp
      Project") and press "F5" to start your MITK AwesomeApp.
</ol>

\note Just opening AwesomeProject.sln from your explorer by double-cliking won't
allow you to start or debug your application because the required environment
variables would be missing. Use the supplied batch files or set your PATH variable
accordingly.

\section HowToNewProjectAddingMITKFunctionality I want to use some MITK plugin but
it is not available

Due to the sheer number of MITK plugins not every plugin is activated by default.
To activate a specific plugin (again replace paths as needed):
<ol>
 <li> Start "cmake-gui" and set the binary directory to
      "D:/AwesomeProject-superbuild/MITK-superbuild/MITK-build/", the source will
      adjust automatically and you will see new settings appear.
 <li> Navigate to the plugin you want to use (e.g. "MITK_BUILD_org.mitk.gui.qt.segmentation")
      and tick the checkbox behind it
 <li> Press "Configure" until no new variables appear and then "Generate".
 <li> Build MITK using your development tool (as in
      \ref HowToNewProjectCompilingLinuxMakefiles or \ref HowToNewProjectCompilingVisualStudio
      only in the "D:/AwesomeProject-superbuild/MITK-superbuild/MITK-build/" directory )
 <li> Start "cmake-gui" and set the binary directory to
      "D:/AwesomeProject-superbuild/AwesomeProject-build/", the source will adjust
      automatically and you will see new settings appear.
 <li> Press "Configure" until no new variables appear and then "Generate".
 <li> Build your project
 <li> Start your application
</ol>

\note If you want to use an application provided by MITK (e.g. MITK Workbench) you
have to tick the appropriate checkbox as well (in this case MITK_BUILD_APP_Workbench)
and build MITK. Do note, that this application will be located in the bin directory
of the "D:/AwesomeProject-superbuild/MITK-superbuild/MITK-build/" folder.


\section HowToNewProjectAdvancedInformation Information for advanced users

\subsection HowToNewProjectCustomizingMITK Customizing MITK

You can either inject an already build MITK to be used by your project or configure
some MITK options directly in your project's superbuild configuration if MITK is
going to be build inside your project.

\subsection HowToNewProjectCustomizingMITKInjectMITK Inject a MITK build

By setting the \b EXTERNAL_MITK_DIR \b variable in your project's superbuild
%CMake configuration to a MITK build directory (containing the MITKConfig.cmake)
you can skip the MITK build process.

If MITK is the only external project in your project, you might want to disable
the superbuild of your project completely (set <your-proj-name>_USE_SUPERBUILD
to OFF or edit your CMakeLists.txt file to set it to OFF by default) and set
the \b MITK_DIR \b %CMake variable to your MITK build directory.

\subsection HowToNewProjectCustomizingMITKConfigure Configure the MITK superbuild

If MITK is being build inside your project's superbuild process, you can enable
the use of certain third-party libraries inside of MITK. The following variables
control the MITK configuration:

<ul>
 <li> \b MITK_USE_BLUEBERRY Enable the use of the BlueBerry application framework
 <li> \b MITK_USE_CTK Download, compile, and use CTK in MITK
 <li> \b MITK_USE_DCMTK Download, compile, and use DCMTK in MITK
 <li> \b MITK_USE_Qt6 Use the Qt 6 framework in MITK
</ul>

You can also inject already build third-party libraries from inside your project's
superbuild in the MITK superbuild by using any of the following %CMake variables:

<ul>
 <li> \b MITK_CTK_DIR Reuse a CTK build directory in MITK.
 <li> \b MITK_DCMTK_DIR Reuse a DCMKT build directory in MITK.
 <li> \b MITK_GDCM_DIR Reuse a GDCM build directory in MITK.
 <li> \b MITK_ITK_DIR Reuse a ITK build directory in MITK.
 <li> \b MITK_VTK_DIR Reuse a VTK build directory in MITK.
</ul>

If the corresponding \b MITK_USE_<proj> \b  option is set to on, the MITK
superbuild will use the provided build directory instead of building the
project itself.

You can also control the source code location for MITK in your project's
superbuild configuration by using the following %CMake variables:

<ul>
 <li> \b MITK_SOURCE_DIR The path to the MITK source directory. If the value
      for this variable is non-empty, the variables below are ignored.
 <li> \b MITK_GIT_REPOSITORY The Git repository containing the MITK source code.
 <li> \b MITK_GIT_TAG The hash id, tag or branch name used for a checkout
      from MITK_GIT_REPOSITORY.
</ul>

\subsection HowToNewProjectProjectStructure Project Structure

If you are using the superbuild feature of the generated project (the default),
you might want to familiarise yourself with the layout of your build tree.
The top-level build directory which you specified in %CMake when configuring
your project will contain all the required dependencies.

Suppose we call our project MyProject and the build directory is
"C:\MyProject-superbuild". Then the layout looks something like this:

MyProjectLayout.png The top-level directory contains the source code and the
build directories from the dependencies of your project. In the current case,
the only dependency of MyProject is MITK, which in turn has downloaded and built
its own dependencies (CTK, DCMTK, ITK, etc.). The "real" build tree for your
project is located in MyProject-superbuild/MyProject-build, so point the
%CMake-GUI to this build directory if you want to change the set of enabled
plug-ins for example.

Further, you should open the MyProject.sln solution file (for Visual Studio)
or execute "make" in the MyProject-superbuild/MyProject-build/ directory.
Only for the very first time or if you want to update and newly build the
project's dependencies should you use the project files in the
MyProject-superbuild directory directly.

The same applies for the MyProject-superbuild/MITK-superbuild directory. This
directory contains the MITK superbuild, nested inside your project's superbuild.
If you want to change %CMake options for MITK, use the
MyProject-superbuild/MITK-superbuild/MITK-build build directory.

\imageMacro{HowToNewProject-MyProjectLayout.png,"Layout of MyProject",4.02}

\subsection HowToNewProjectPackaging Packaging

You can create deployable packages of your project
for all supported operating systems my building the PACKAGE target. On Linux,
this will create a tarball, on MacOS a .dmg file, and on Windows a zipball and
an NSIS installer (if NSIS is installed and found).

You can read more about deployment \ref DeploymentPage "here".

*/
