Dear Stefan,
 
I just wanted to tell you that, after your suggestions, everything worked fine.
The problem apparently was, indeed, me enabling the MITK_USE_PYTHON flag in the cmake gui...
for some reason I still don't know this resulted in the errors I had... however the basic build afterwards
succeeded.
 
Thanks a lot!
 
Kind regards,
Ivaylo
 
Gesendet: Mittwoch, 26. Juni 2019 um 11:03 Uhr
Von: "Dinkelacker, Stefan" <[email protected]>
An: "Ivaylo Angelov" <[email protected]>
Betreff: RE: RE: RE: [mitk-users] machine type error during MITK - superbuild

Hi, no need to, I already added the list to Cc again. It would not work for the list anyway as we have a 600 or 800 KB limit for attachments there. To be honest, I did not look into your 11 MB logfiles. It’s not considered very polite to expect others to crawl through such amounts of data. I would advise to focus on the actual errors and posting them instead if still necessary. J The more specific a question is asked, the more likely you will get specific answers.

 

From: Ivaylo Angelov [mailto:[email protected]]
Sent: Wednesday, June 26, 2019 10:56 AM
To: Dinkelacker, Stefan <[email protected]>
Subject: Aw: RE: RE: [mitk-users] machine type error during MITK - superbuild

 

Hello Stefan,

 

I am sorry, that was not on purpose.
Should I resend it with another destination address so it's on the list?

Kind regards,

Ivaylo

 

Gesendet: Mittwoch, 26. Juni 2019 um 10:44 Uhr
Von: "Dinkelacker, Stefan" <[email protected]>
An: "Ivaylo Angelov" <[email protected]>
Cc: "'[email protected]'" <[email protected]>
Betreff: RE: RE: [mitk-users] machine type error during MITK - superbuild

Hi Avaylo,

 

please keep the conversation on the list.

 

Unfortunately there are no attachments to your mail. However, I would recommend to simply start by doing a default build without checking/unchecking specific features and then start to enable/disable features when everything works.

 

Best,

Stefan

 

From: Ivaylo Angelov [mailto:[email protected]]
Sent: Wednesday, June 26, 2019 10:41 AM
To: Dinkelacker, Stefan <[email protected]>
Subject: Aw: RE: [mitk-users] machine type error during MITK - superbuild

 

Dear Stefan,

 

thank you very much for your help! 
I installed cmake 3.13 and it seems to have solved the previous issue.

Unfortunately, something different appeared, that I would like to know your opinion about.

I am sending the current error list together with the whole Visual Studio output of my ALLBUILD with this mail.

 

I should mention that, choosing the components in cmake, I also included the build of all examples as well as the MITK_USE_Python flag ... given that lots of the errors seem to be python - related... could it have to do something with that?

 

This was yesterday... I tried rebuilding the MITK-build today, which ended in 18 succeeding, 5 failing....

for this build I also appended the error list and the whole Visual Studio output.

 

I don't have any idea what to do by now, I just hope it may be something more or less obvious for the people associated with the project... I would appreciate your help on that.

 

Kind regards

 

Ivaylo Angelov

 

 

 

Gesendet: Dienstag, 25. Juni 2019 um 12:50 Uhr
Von: "Dinkelacker, Stefan" <[email protected]>
An: "Ivaylo Angelov" <[email protected]>, "[email protected]" <[email protected]>
Betreff: RE: [mitk-users] machine type error during MITK - superbuild

Hi Avaylo,

 

CMake 3.14 uses a new approach to set the generator platform (i.e. x64, which is correct). However, it is not supported in v2018.04.2 but it is supported in the releases/2018-04 branch, which you can checkout from https://phabricator.mitk.org/source/mitk.git, e.g.:

 

git clone -b releases/2018-04 https://phabricator.mitk.org/source/mitk.git MITK

 

If you want to stick with v2018.04.2, use CMake 3.13 instead of CMake 3.14.

 

Best,

Stefan

 

From: Ivaylo Angelov [mailto:[email protected]]
Sent: Tuesday, June 25, 2019 9:46 AM
To: [email protected]
Subject: [mitk-users] machine type error during MITK - superbuild

 

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
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to