Hi, just FYI, we are tracking this at http://bugs.mitk.org/show_bug.cgi?id=16886
Thanks, Sascha On 01/23/2014 10:57 AM, Urban Simoncic wrote: > Hi, > > thanks for the quick response. Using the Doxygen 1.8.0 solved the issue. > > Best, > Urban > > On 23.1.2014 10:23, Sascha Zelzer wrote: >> Hi, >> >> we actually try hard to not depend on the user to select the "right" >> set of CMake options. Missing required options are either >> automatically enabled or certain features in MITK are disabled if some >> options are set to OFF. That being said, I am aware that with such an >> amount of possible options and external dependencies there is always >> the possibility of bugs. >> >> In your case, you seem to be using an unsupported Doxygen version. The >> CMake configuration step of MITK (not of the superbuild) should warn >> you about that. Doxygen is used to generate the plug-in manuals and >> some versions other than 1.8.0 produce build errors (and some don't >> but produce garbage...). >> >> Error FODC0002 in >> file:///C:/MITK/sb/MITK-build/Plugins/org.mitk.gui.qt.igttracking/documentation/UserManual/html/index.qhp, >> at line 29, column 14: Opening and ending tag mismatch. >> >> >> You could either install Doxygen 1.8.0 or disable the documentation >> generation process by setting MITK_DOXYGEN_GENERATE_QCH_FILE to OFF. >> >> Best, >> Sascha >> >> On 01/23/2014 02:16 AM, Urban Simoncic wrote: >>> Hi, >>> >>> sorry for bothering again with the build error, but things are still not >>> clear to me. I can build the MITK with the default CMake settings. But >>> that is the only case when my compilation is successful; I played with >>> some other CMake settings, but always get a compilation error. >>> >>> E.g. I selected MITK_BUILD_ALL_APPS, MITK_BUILD_ALL_PLUGINS and >>> MITK_BUILD_ALL_EXAMPLES, but I got an error early in the compilation >>> process. I somehow figured out that I may have to select also the Boost >>> library and with that setting the compilation was "almost" successful. >>> By "almost" successful compilation I mean that some applications are >>> compiled correctly and I can run them, but not the MITK Workbench. The >>> compiler output is attached. >>> >>> So, is there an easy way to figure out which combination of CMake flags >>> (and other CMake settings and external programs on the computer) should >>> work? What else I have to set to ON if I select the MITK_BUILD_ALL_APPS, >>> MITK_BUILD_ALL_PLUGINS and MITK_BUILD_ALL_EXAMPLES? In other words: what >>> is wrong with the CMake setting that produced the attached erroneous >>> compiler output? >>> >>> Best, >>> Urban >>> >>> On 20.1.2014 18:19, Sascha Zelzer wrote: >>>> Hi, >>>> >>>> it usually means that there was a network connection problem and the >>>> tarball could not be retrieved correctly. In the MITK-superbuild.sln >>>> solution, try to rebuild the tinyxml project (tinyxml context menu -> >>>> project only -> rebuild). >>>> >>>> Best, >>>> Sascha >>>> >>>> On 01/20/2014 09:44 AM, Urban Simoncic wrote: >>>>> Hi, >>>>> >>>>> I used version 2013.12 and I added PATH from .bat files and MITK >>>>> Workbench works. My next step was to use the Plugin generator. The >>>>> Application builds OK and I am able to run it, but building of one >>>>> target fails. I think the problem must be in the output below (part of >>>>> the compiler output). Does it mean that it is something wrong with the >>>>> downloaded library 'tinyxml'? >>>>> >>>>> Best, >>>>> Urban >>>>> >>>>> 2> CustomBuild: >>>>> 2> Building Custom Rule C:/MITK/sb/MITK/CMakeLists.txt >>>>> 2> CMake does not need to re-run because >>>>> C:\MITK\sb\MITK-superbuild\CMakeFiles\generate.stamp is up-to-date. >>>>> 2> Creating directories for 'tinyxml' >>>>> 2> Performing download step (download, verify and extract) for >>>>> 'tinyxml' >>>>> 2> -- downloading... >>>>> 2> src='http://mitk.org/download/thirdparty/tinyxml_2_6_2.tar.gz' >>>>> 2> >>>>> dst='C:/MITK/sb/MITK-superbuild/tinyxml-cmake/src/tinyxml_2_6_2.tar.gz' >>>>> >>>>> 2> timeout='none' >>>>> 2> CMake Error at >>>>> tinyxml-cmake/src/tinyxml-stamp/download-tinyxml.cmake:9 (file): >>>>> 2> file DOWNLOAD HASH mismatch >>>>> 2> for file: >>>>> [C:/MITK/sb/MITK-superbuild/tinyxml-cmake/src/tinyxml_2_6_2.tar.gz] >>>>> 2> expected hash: [c1b864c96804a10526540c664ade67f0] >>>>> 2> actual hash: [d41d8cd98f00b204e9800998ecf8427e] >>>>> >>>>> On 19.1.2014 13:27, Sascha Zelzer wrote: >>>>>> Hi Urban, >>>>>> >>>>>> just as a side note: The VTK library path issue Stefan mentioned >>>>>> applies to the current MITK master only. Unless you have good reasons >>>>>> to use the MITK master, you should be using the latest MITK release >>>>>> (which would be 2013.12). The batch files generated when configuring >>>>>> the 2013.12 sources are complete and should "just work". >>>>>> >>>>>> Best, >>>>>> Sascha >>>>>> >>>>>> On 18/01/2014 21:47, Urban Simoncic wrote: >>>>>>> Hi, >>>>>>> >>>>>>> thanks for all the info on building process. Now I can run the MITK >>>>>>> Workbench that I build myself and I should be ready to start >>>>>>> experimenting with the code. >>>>>>> >>>>>>> Best, >>>>>>> Urban >>>>>>> >>>>>>> On 18.1.2014 16:19, Kislinskiy, Stefan wrote: >>>>>>>> Hi, >>>>>>>> >>>>>>>> there are batch files in the build directory of MITK named >>>>>>>> StartVS_debug.bat and StartVS_release.bat which set up all paths >>>>>>>> either for debug or release mode. Currently they doesn't include >>>>>>>> the >>>>>>>> VTK path which will be fixed by the next VTK release. Until then >>>>>>>> you >>>>>>>> must manually add the VTK path. Since every CMake run will reset >>>>>>>> the >>>>>>>> batch files I recommend to copy the complete "PATH=..." line into a >>>>>>>> separate text file, replace "debug" or "release" by >>>>>>>> "$(Configuration)" or "$(ConfigurationName)" in case of VS2008, and >>>>>>>> copy the modified line right into the project settings of the >>>>>>>> mitkWorkbench (Project Settings->Configuration >>>>>>>> Properties->Debugging->Environment). Ensure that you selected both >>>>>>>> debug and release mode at the top of the dialog to apply the >>>>>>>> settings to all configurations. This way you don't need the batch >>>>>>>> files at all and can use the MITK solution file directly. The >>>>>>>> project settings are not overwritten by CMake. Don't forget to add >>>>>>>> the VTK path as well. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Stefan >>>>>>>> ________________________________________ >>>>>>>> Von: Urban Simoncic [[email protected]] >>>>>>>> Gesendet: Freitag, 17. Januar 2014 21:39 >>>>>>>> An: Kislinskiy, Stefan; Zelzer, Sascha; >>>>>>>> [email protected] >>>>>>>> Betreff: Re: AW: [mitk-users] Build error >>>>>>>> >>>>>>>> Hi, >>>>>>>> thanks for that advice. I have been able to build the application >>>>>>>> with >>>>>>>> MSVC 2010 Express and Windows SDK. After manually setting the Path >>>>>>>> for >>>>>>>> some dll's, the MITK Workbench starts a command line window and >>>>>>>> runs >>>>>>>> something and then ends. I can't read what is going on there. Does >>>>>>>> the >>>>>>>> MITK Workbench stop because not all shared libraries are in >>>>>>>> Path? Is >>>>>>>> there any automated way to set the Path for all the shared >>>>>>>> libraries? >>>>>>>> >>>>>>>> Best, >>>>>>>> Urban >>>>>>>> >>>>>>>> On 17.1.2014 14:32, Kislinskiy, Stefan wrote: >>>>>>>>> As an addition I would like to say that we support MSVC 2010 and >>>>>>>>> 2012 as well. However, to get things up and running with MSVC 2012 >>>>>>>>> you need to patch and compile Qt manually. Personally I would >>>>>>>>> recommend MSVC 2010 which is more feature rich in its Express >>>>>>>>> edition than MSVC 2008. In any case, it you use an express edition >>>>>>>>> you should always install the Windows SDK as well. >>>>>>>>> >>>>>>>>> -----Ursprüngliche Nachricht----- >>>>>>>>> Von: Sascha Zelzer [mailto:[email protected]] >>>>>>>>> Gesendet: Freitag, 17. Januar 2014 14:17 >>>>>>>>> An: [email protected]; Kislinskiy, Stefan; >>>>>>>>> [email protected] >>>>>>>>> Betreff: Re: [mitk-users] Build error >>>>>>>>> >>>>>>>>> Hi Urban, >>>>>>>>> >>>>>>>>> The documentation is up-to-date and VS2008 SP1 is supported. >>>>>>>>> However, we are using the professional version and do not test >>>>>>>>> regularly with the express edition (the documentation lacks in >>>>>>>>> that >>>>>>>>> respect). >>>>>>>>> >>>>>>>>> Please try to find the "mc.exe" executable on your system (the >>>>>>>>> "message compiler"). Maybe the express edition does not ship >>>>>>>>> it. It >>>>>>>>> is probably included in some Windows SDK as an extra download. If >>>>>>>>> you do have it installed, you could help Poco find the mc.exe by >>>>>>>>> pointing CMAKE_MC_COMPILER within the Poco CMake configuration to >>>>>>>>> its path. >>>>>>>>> >>>>>>>>> Best, >>>>>>>>> Sascha >>>>>>>>> >>>>>>>>> On 01/17/2014 02:03 PM, Urban Simoncic wrote: >>>>>>>>>> Hi Stefan, >>>>>>>>>> >>>>>>>>>> thank you for quick response. I have MSVC2008 with SP1 - see the >>>>>>>>>> attached image to determine what I have. Can I use the newer >>>>>>>>>> MSVC? I >>>>>>>>>> installed MSVC2008 just because the documentation claims support >>>>>>>>>> for >>>>>>>>>> MSVC2008 SP1. If that is outdated, please let me know which MSVC >>>>>>>>>> and >>>>>>>>>> Qt shall I use (possibly MSVC Express edition that is free). >>>>>>>>>> >>>>>>>>>> Best, >>>>>>>>>> Urban >>>>>>>>>> >>>>>>>>>> On 17.1.2014 13:34, Kislinskiy, Stefan wrote: >>>>>>>>>>> Hi Urban, >>>>>>>>>>> >>>>>>>>>>> The CMake configuring of PocoFoundation fails: >>>>>>>>>>> >>>>>>>>>>> 4>CMake Error at Foundation/CMakeLists.txt:18 (message): >>>>>>>>>>> 4> message compiler not found: required to build >>>>>>>>>>> 4>-- Configuring incomplete, errors occurred! >>>>>>>>>>> >>>>>>>>>>> You might want to have a look at >>>>>>>>>>> Poco-build/Foundation/CMakeLists.txt. There is a comment that >>>>>>>>>>> states VS2008+ is needed. Do you already installed the Service >>>>>>>>>>> Pack for VS2008? >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> Stefan >>>>>>>>>>> ________________________________________ >>>>>>>>>>> Von: Urban Simoncic [[email protected]] >>>>>>>>>>> Gesendet: Freitag, 17. Januar 2014 13:06 >>>>>>>>>>> An: [email protected] >>>>>>>>>>> Betreff: [mitk-users] Build error >>>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> I am trying to build the MITK for a few days, without much >>>>>>>>>>> success. >>>>>>>>>>> Because I don't know much about the MITK code, I have hard >>>>>>>>>>> time to >>>>>>>>>>> locate the error from the compiler output. So, I am sending the >>>>>>>>>>> output of the compiler, hoping that someone can tell me what >>>>>>>>>>> I am >>>>>>>>>>> doing wrong. >>>>>>>>>>> >>>>>>>>>>> Thank you, >>>>>>>>>>> Urban >>>>>>>>>>> PS: I am working on Win 7 64 bit, using MSVC 2008 Express. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >> ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
