Page MenuHomePhabricator

The compiled MITK has no source file
Closed, InvalidPublic

Description

My computer software configuration is as follows:

when i complie MITK by cmake, and i click Configure, it just display :

Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.22621.
Performing Test HAS_FLAG_-std=c17
Performing Test HAS_FLAG_-std=c17 - Failed

/------- FEATURE SUMMARY FOR MITK-superbuild -------
/-- The following OPTIONAL packages have been found:

  • OpenSSL

/-- The following REQUIRED packages have been found:

  • Qt5Core (required version >= 5.15.2)
  • Qt5Concurrent
  • Qt5Gui (required version >= 5.15.2)
  • Qt5OpenGL
  • Qt5PrintSupport
  • Qt5Script
  • Qt5Sql
  • Qt5Svg
  • Qt5Widgets
  • Qt5Xml
  • Qt5Network (required version >= 5.15.2)
  • Qt5XmlPatterns
  • Qt5Qml (required version >= 5.15.2)
  • Qt5QmlModels (required version >= 5.15.2)
  • Qt5Quick (required version >= 5.15.2)
  • Qt5WebChannel (required version >= 5.15.2)
  • Qt5Positioning (required version >= 5.15.2)
  • Qt5WebEngineCore (required version >= 5.15.2)
  • Qt5WebEngineWidgets
  • Qt5UiTools
  • Qt5Help
  • Qt5LinguistTools
  • Qt5 (required version >= 5.12.9)
  • Git

Configuring done

And when i click Genetate and Open project , the generated project does not have source, it is empty!!!

image.png (1×1 px, 106 KB)

Event Timeline

kislinsk added a subscriber: kislinsk.

Please see the build instructions. Long story short: MITK uses a superbuild, meaning it has two build levels. What you see is the outer level, called superbuild. The superbuild downloads, configures, and builds all required third-party libraries (except Qt) automatically. One of the projects of the superbuild is the MITK build itself, the inner level. As soon as the MITK-Configure project was successfully built on superbuild level, you find a populated MITK-build folder in your superbuild folder. From then on you can set it as build directory in CMake to change the configuration of MITK itself, for example, enable plugins and so on...

We have a few convenience features so you can set common configurations of MITK right in the superbuild without the need to switch to the MITK build level after the superbuild. For example, in CMake set MITK_BUILD_CONFIGURATION to MitkWorkbench Release. This will pass down all necessary CMake settings to the MITK build itself to build MITK as you know it from the official installers.

In case you want to implement something in MITK, please also see the MITK-ProjectTemplate. For the very start though, just go ahead and build vanilla MITK as advised above. Everything else can then be adjusted later.