n what is going wrong. Getting our packaging script
>> right on macOS was a little nightmare and we still have a custom fix script
>> after the actual packaging to get things working (maybe that’s already a
>> good hint):
>> https://github.com/MITK/MITK/blob/v2018.04.2/CMake/F
y autoload module, making the autoloading pretty much
> pointless, right? However, we didn’t notice we have one of such a
> dependency last minute before the actual release and it only showed up on
> macOs so we decided to work around this by creating symlinks to autoload
> modules besid
...@gmail.com]
Sent: Tuesday, June 25, 2019 2:01 PM
To: Dinkelacker, Stefan
Cc: mitk-users@lists.sourceforge.net
Subject: Re: [mitk-users] [Migrating to MITK v2018.04.2] Problems with external
applications
Dear all,
We are experiencing a problem packaging our application in macOS.
First, let me
an <
> s.dinkelac...@dkfz-heidelberg.de> wrote:
>
> Hi, good to hear. Do you have any hints on the missing ID issue?
>
>
>
> Regarding macOS packaging, well, it’s complicated and we would need
> specific information on what is going wrong. Getting our packaging script
> ri
: Dinkelacker, Stefan
Cc: mitk-users@lists.sourceforge.net
Subject: Re: [mitk-users] [Migrating to MITK v2018.04.2] Problems with external
applications
Hi all!
Regarding the ID issue, I did three things on the Applications/CMakeLists.txt
in my project folder. (For context, I have a variable called
-users@lists.sourceforge.net
Subject: Re: [mitk-users] [Migrating to MITK v2018.04.2] Problems with external
applications
Hello!
I've managed to compile properly the project properly by following both the
Diffusion app and the Workbench. It works well on Ubuntu, even the packaging.
Now our foc
MITK v2018.04.2] Problems with external
applications
Dear MITKers,
Thank you very much for your help so far.
We have other inquiries regarding the upgrade of our app. For context, I'll
repeat some of the things I've said already in this thread. We are in the
process of migrating our a
Dear MITKers,
Thank you very much for your help so far.
We have other inquiries regarding the upgrade of our app. For context, I'll
repeat some of the things I've said already in this thread. We are in the
process of migrating our application from v2016.03 to v2018.04.2, following
the external pr
