Dear Sir or Madam,
 
after a recent mail of mine regarding a problem I received multiple suggestions which I tried in order
to solve the issue.
Unfortunately, I still have the problem, which is why I am hereby following your suggestions of turning to the mailing list.
 
I am trying to build the MITK - superbuild like it is shown in your developer tutorial.
Here is what I have:
 
-> Microsoft Visual Studio Community, version 15.9.13 (no current updates available, so up-to-date)
-> Qt 5.12.4 added to my path variable(on their website https://www.qt.io/download I chose the open source version, given that the commercial one just  offers a trial and I am just a student, so not able to pay the monthly fee for the commercial version)
-> cmake 3.14.5
 
As you suggested, I cloned the repository and checked out the v2018.04.2 tag.
I also opened a folder for the template and one for the binaries called MITK - superbuild.
 
So far so good.
 
I then go to cmake and do as you say in the tutorial, although generator choices are slightly different.
(I sent a screenshot of that too.)
I can choose from: "Visual Studio 16 2019", "Visual Studio 15 2017", "Visual Studio 14 2015" ....
Below it lets me choose an optional platform for the generator, saying that it is Win32 by default.
My options here are "ARM64", "ARM", "Win32", "x64".
Wanting to build for a 64 bit machine, I choose "x64" and continue as described in the tutorial.
 
Doing the superbuild I get a bunch of errors on multiple builds (e.g. on the HDF5) of the sort:
"LNK1112    module machine type 'x86' conflicts with target machine type 'x64'"
(I added a text file to that mail with the whole error output).
 
I tried a lot of stuff by now... different releases, different qt versions.... nothing works which is quite depressing.
I would appreciate your help a lot and hope to hear from you soon.
 
Kind regards
 
Ivaylo Angelov
_______________________________________________
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to