Hi Pierre-Jean, I am also currently test-compiling MITK 2018.04 with Visual Studio 2017 / Qt 5.11.1. I cannot provide a solution but perhaps hint into a direction:
I had the same error message and basically this comes up when the Core module of MITK cannot be defined because some dependency is missing. (cannot recall the exact thing that was missing). What you can do to hunt this down: - in the mitk-superbuild.sln solution, explicitly compile all of the projects like VTK/DCMTK/ITK etc. one by one, look for problems in their build. This could point you into the right direction. - if those builds all pass and you still get the same error in MITK-Configure, you need to debug into the CMake code of CMake/mitkFunctionCreateModule.cmake (i.e. add messages at interesting places when the module name is "Core"). In my case I found one of the checks between lines 208 and 250 failing (checking for dependencies and/or suppressed modules) Unfortuately I could not generalize a helpful error message out of the thing that was missing in my case. This is because usually it is not considered a problem when a certain module is missing due to unmet dependencies - you would just get a nice list of deactivated modules in the end of the Configuration step. It ist just that the MitkCore module is a little special and required by everything else. Someone would need to find a good place to add a check for this module and then stop configuration early.. Hope this helps a little, kind regards, Daniel > Pierre-Jean Petitprez <pierre-jean.petitp...@hrv-simulation.com> hat am 22. > Januar 2019 um 11:15 geschrieben: > > > Hi Stefan, > Thank you for the hints. MITK-configure indeed fails. The CMake logs > give me this error: > CMake Error at Modules/Core/CMakeLists.txt:34 (message): > Core target MitkCore does not exist > CMake Error at Modules/Core/CMakeLists.txt:54 (target_compile_definitions): > Cannot specify compile definitions for target "MitkCore" which is not built > by this project. > Call Stack (most recent call first): > Modules/Core/CMakeLists.txt:57 (_itk_create_factory_register_manager) > CMake Error at Modules/Core/CMakeLists.txt:60 (target_link_libraries): > Cannot specify link libraries for target "MitkCore" which is not built by > this project. > > I can't find anything in the CMake options that could help fixing this > error though. Do you have any idea? Thanks for the help. > > Le 21/01/2019 à 23:02, Dinkelacker, Stefan a écrit : > > Hi, this usually means that one or more projects did not built successfully > > before MITK-build. At this state It is likely that it is MITK-configure. > > This project basically runs CMake to configure MITK. You can also do this > > manually and easily see what the actual problem is. When opening CMake GUI > > and change the the build directory from D:/your/path/MITK-superbuild to > > D:/your/path/MITK-superbuild/MITK-build, the variables you see should > > change from the superbuild configuration to the MITK configuration. Click > > on Configure/Generate and wait until it fails. Note that this output should > > also already be available in the superbuild solution when the build fails > > and you scroll up in the output Window. However, I prefer the former way as > > you can immediately change the configuration to fix the problem. After the > > configuration is complete, you can open MITK.sln instead of > > MITK-superbuild.sln and build MITK itself. > > ________________________________________ > > Von: Pierre-Jean Petitprez <pierre-jean.petitp...@hrv-simulation.com> > > Gesendet: Montag, 21. Januar 2019 18:40 > > An: mitk-users@lists.sourceforge.net > > Betreff: [mitk-users] Issues when compiling MITK on MSVC2017 > > > > Hi everyone, > > I encounter some issues when trying to compile MITK (2018.04, but it > > also happens with the latest version on git/master) on Windows 10 with > > Visual Studio 2017 (version 15.9.5). The Superbuild fails when trying to > > compile MITK-build with this error: > > MSB1009 : Project file does not exist. > > I can't find any reason in the logs why this happens. Has anybody any > > clue of why this issue happens and how to fix the build? > > > > Thank you, > > > > Kind regards > > Pierre > > > > > > _______________________________________________ > > mitk-users mailing list > > mitk-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/mitk-users > _______________________________________________ > mitk-users mailing list > mitk-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mitk-users _______________________________________________ mitk-users mailing list mitk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mitk-users
