Re: [mitk-users] PluginGenerator and ProjectTemplate

[Dinkelacker, Stefan]

Thank you Matthias,


I will fix it and add you as co-author to the commit.


Best,


Stefan



Von: Noll, Matthias 
Gesendet: Montag, 10. Januar 2022 15:56
An: Dinkelacker, Stefan; Nil Goyette
Cc: mitk-users@lists.sourceforge.net
Betreff: RE: [mitk-users] PluginGenerator and ProjectTemplate

Dear Stefan,

I ran into the same problem as Nil did concerning the Qt5::WebEngine not found 
error.
I’ve build version 2021.02 of mitk using the superbuild option and then 
deployed a ProjectTemple using the PuginGenerator.

The Qt5::WebEngine error arises, when compiling the deployed ProjectTemplate. 
And it’s the only error I get.
The CmakeLists.txt in the “Apps” folder calls the cmake function 
“mitkFunctionCreateBlueBerryApplication”, where it adds MODULE MitkAppUtil to 
the application. (Btw: The line “mitk_use_modules(TARGET ${MY_APP_NAME} MODULES 
MitkAppUtil)” is redundant here because the module is already being added 
inside “mitkFunctionCreateBlueBerryApplication.cmake#103”.)

The problem seems to be that the module AppUtil sets its qt dependencies as 
follows “set(qt5_depends Qt5|Widgets+WebEngine)”.
You told Nil that the module “infects” the build with this dependency and qt 
does not find the WebEngine lib automatically during superbuild. At least not 
for me and I don’t know why that is. It also does not work for me to manually 
declare the Qt5_WebEngine path in cmake. Initially I did not have WebEngine 
downloaded in my qt dir so I had to modify my qt setup after the superbuild was 
already completed once. Maybe that’s one potential problem?

Anyway, I had a closer look at the AppUtil module. This module seems to use 
only the includes header “”, which is part of 
“Qt5WebEngineCore”. Since there are no other decencies to WebEngine functions 
at this level I figure that it’s not necessary to depend on the entire 
WebEngine module here.

So, changing line 1 in :  
\\MITK2021\src\Modules\AppUtil\CmakeLists.txt
 from
set(qt5_depends Qt5|Widgets+WebEngine)
to only
set(qt5_depends Qt5|Widgets+WebEngineCore)

seems to fix the issue for me.



From: Dinkelacker, Stefan 
Sent: Mittwoch, 7. April 2021 13:00
To: Nil Goyette 
Cc: mitk-users@lists.sourceforge.net
Subject: Re: [mitk-users] PluginGenerator and ProjectTemplate


Hi,



my first guess is that your executable is infected with this dependency from 
MitkAppUtil, which has a PUBLIC package dependency to WebEngine. Usually CMake 
is right in its assumptions regarding find_package(). So a first step would be 
to do a manual find_package for WebEngine and continue from there. If it still 
cannot be found, but other components of Qt were found, double-check your 
installation and maybe manually look for the Config.cmake file in the lib/cmake 
subfolder of your Qt installation. Since you seem to use MITK as library it is 
hard to make better guesses at the moment. I also did not use Qt 5.15 yet, only 
5.12.



Best,

Stefan


Von: Nil Goyette 
Gesendet: Dienstag, 6. April 2021 17:21
An: Dinkelacker, Stefan
Cc: mitk-users@lists.sourceforge.net
Betreff: Re: [mitk-users] PluginGenerator and ProjectTemplate

Hi Stefan,

My module wasn't found because I included "MitkTestingHelper" in the wrong 
place. There was no useful error message so I had to guess it.
But now I have another problem and you may be able to help me. The CMake 
Configure part is ok, but when I click on Generate, I get this error

CMake Error at 
C:/Imeka/mitk/CMake/mitkFunctionCreateBlueBerryApplication.cmake:88 
(add_executable):
Target "MI-Brain" links to target "Qt5::WebEngine" but the target was not
found. Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
Call Stack (most recent call first):
Apps/MI-Brain/CMakeLists.txt:34 (mitkFunctionCreateBlueBerryApplication)
which is surprising because I don't use or try to include WebEngine. A git grep 
WebEngine returns nothing. And I know and verified that I installed WebEngine 
along with Qt 5.15.X. Do you know what is causing this?

NIl

Le lun. 5 avr. 2021, à 19 h 19, Dinkelacker, Stefan 
mailto:s.dinkelac...@dkfz-heidelberg.de>> a 
écrit :

Hi Nil,



you do *not* need to use the ProjectTemplate but it is at least the strongly 
recommended way for new MITK developers to go the framework route with MITK. 
You can still continue using MITK as plain CMake-based toolkit/library. As 
written in T27701, we just want to get rid of the ProjectGeneration part, not 
the PluginGeneration part.



We focus on the ProjectTemplate since we recognized that most of the external 
developers are not primarily developers but scientists and while they usually 
have at least a basic level of knowledge in C++ to get things done, CMake is 
already something different. Using the ProjectTemplate basically means using 
MITK as we do internally (which is a big plus for us regarding support) and 
that people just need to a

Re: [mitk-users] PluginGenerator and ProjectTemplate

[Noll, Matthias]

Dear Stefan,

I ran into the same problem as Nil did concerning the Qt5::WebEngine not found 
error.
I've build version 2021.02 of mitk using the superbuild option and then 
deployed a ProjectTemple using the PuginGenerator.

The Qt5::WebEngine error arises, when compiling the deployed ProjectTemplate. 
And it's the only error I get.
The CmakeLists.txt in the "Apps" folder calls the cmake function 
"mitkFunctionCreateBlueBerryApplication", where it adds MODULE MitkAppUtil to 
the application. (Btw: The line "mitk_use_modules(TARGET ${MY_APP_NAME} MODULES 
MitkAppUtil)" is redundant here because the module is already being added 
inside "mitkFunctionCreateBlueBerryApplication.cmake#103".)

The problem seems to be that the module AppUtil sets its qt dependencies as 
follows "set(qt5_depends Qt5|Widgets+WebEngine)".
You told Nil that the module "infects" the build with this dependency and qt 
does not find the WebEngine lib automatically during superbuild. At least not 
for me and I don't know why that is. It also does not work for me to manually 
declare the Qt5_WebEngine path in cmake. Initially I did not have WebEngine 
downloaded in my qt dir so I had to modify my qt setup after the superbuild was 
already completed once. Maybe that's one potential problem?

Anyway, I had a closer look at the AppUtil module. This module seems to use 
only the includes header "", which is part of 
"Qt5WebEngineCore". Since there are no other decencies to WebEngine functions 
at this level I figure that it's not necessary to depend on the entire 
WebEngine module here.

So, changing line 1 in :  
\\MITK2021\src\Modules\AppUtil\CmakeLists.txt
 from
set(qt5_depends Qt5|Widgets+WebEngine)
to only
set(qt5_depends Qt5|Widgets+WebEngineCore)

seems to fix the issue for me.



From: Dinkelacker, Stefan 
Sent: Mittwoch, 7. April 2021 13:00
To: Nil Goyette 
Cc: mitk-users@lists.sourceforge.net
Subject: Re: [mitk-users] PluginGenerator and ProjectTemplate


Hi,



my first guess is that your executable is infected with this dependency from 
MitkAppUtil, which has a PUBLIC package dependency to WebEngine. Usually CMake 
is right in its assumptions regarding find_package(). So a first step would be 
to do a manual find_package for WebEngine and continue from there. If it still 
cannot be found, but other components of Qt were found, double-check your 
installation and maybe manually look for the Config.cmake file in the lib/cmake 
subfolder of your Qt installation. Since you seem to use MITK as library it is 
hard to make better guesses at the moment. I also did not use Qt 5.15 yet, only 
5.12.



Best,

Stefan


Von: Nil Goyette 
Gesendet: Dienstag, 6. April 2021 17:21
An: Dinkelacker, Stefan
Cc: mitk-users@lists.sourceforge.net
Betreff: Re: [mitk-users] PluginGenerator and ProjectTemplate

Hi Stefan,

My module wasn't found because I included "MitkTestingHelper" in the wrong 
place. There was no useful error message so I had to guess it.
But now I have another problem and you may be able to help me. The CMake 
Configure part is ok, but when I click on Generate, I get this error

CMake Error at 
C:/Imeka/mitk/CMake/mitkFunctionCreateBlueBerryApplication.cmake:88 
(add_executable):
Target "MI-Brain" links to target "Qt5::WebEngine" but the target was not
found. Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
Call Stack (most recent call first):
Apps/MI-Brain/CMakeLists.txt:34 (mitkFunctionCreateBlueBerryApplication)
which is surprising because I don't use or try to include WebEngine. A git grep 
WebEngine returns nothing. And I know and verified that I installed WebEngine 
along with Qt 5.15.X. Do you know what is causing this?

NIl

Le lun. 5 avr. 2021, à 19 h 19, Dinkelacker, Stefan 
mailto:s.dinkelac...@dkfz-heidelberg.de>> a 
écrit :

Hi Nil,



you do *not* need to use the ProjectTemplate but it is at least the strongly 
recommended way for new MITK developers to go the framework route with MITK. 
You can still continue using MITK as plain CMake-based toolkit/library. As 
written in T27701, we just want to get rid of the ProjectGeneration part, not 
the PluginGeneration part.



We focus on the ProjectTemplate since we recognized that most of the external 
developers are not primarily developers but scientists and while they usually 
have at least a basic level of knowledge in C++ to get things done, CMake is 
already something different. Using the ProjectTemplate basically means using 
MITK as we do internally (which is a big plus for us regarding support) and 
that people just need to add modules, plugins, or dependencies to an existing 
application backed by examples/templates.



When a module is suddenly missing it is probably related to a missing implicit 
dependency that is not there anymore (we revisited the ITK dependencies

Re: [mitk-users] PluginGenerator and ProjectTemplate

[Nil Goyette]

Hi Stefan,

as always, thank you for your answer.

   1. "Spare the last step" Yes, of course, it would fix the recompilation
   problem but not the others (see april 21th message). And as I said it's not
   compatible with our build system. We're preparing the mitk build in our
   cicd and using it to build our own project when we modify it. This is much
   faster than building the whole mitk+imeka project. We could abandon this
   method, but it's not worth it if it only fixes a part of the problem.
   2. Haha, yes, there is some wrong command line usage. I usually use
   cmake-gui so I don't deactivate the testing twice. And I don't specify the
   Qt directory if cmake doesn't ask for it.
   3. Yes, thanks again for the shortcut. It's nice to learn little tricks
   like that.
   4. I totally agree with your last sentence: it should be done in a few
   seconds. This is indeed the expected result.

I tested on a Linux vm with the exact same results (mitk recompilation). I
know that it's not supposed to happen but it's clearly happening and I
still have all the same problems. I would gladly use the extension method
but it's not working as intended. Do you have any other ideas on how to fix
this magical problem? At that point, I'd prefer trying the "mitk as a
library" method again, but it would be nice to have a minimal working
example (applications, modules, plugins, cmakelist). I usually look at
MitkDiffusion for examples but there's no cmake files anymore so it looks
like Peter switched too!

Nil

-- 
During this time of social distancing, we offer free webinars on subjects 
that matter. 

CONFIDENTIALITY NOTICE: This 
message, and any attachments, is intended only for the use of the addressee 
or his authorized representative. It may contain information that is 
privileged, confidential and exempt from disclosure under applicable law. 
If the reader of this message is not the intended recipient, or his 
authorized representative, you are hereby notified that any dissemination, 
distribution or copying of this message and any attachments is strictly 
prohibited. The integrity of this message cannot be guaranteed on the 
Internet, IMEKA shall not be liable for its content if altered, changed or 
falsified. If you have received this message in error, please contact 
immediately the sender and delete this message and any attachments from 
your system.


AVIS DE CONFIDENTIALITÉ : Ce message, ainsi que tout fichier 
qui y est joint, est destiné exclusivement aux personnes à qui il est 
adressé. Il peut contenir des informations de nature confidentielle qui ne 
doivent être divulguées en vertu des lois applicables. Si vous n'êtes pas 
le destinataire de ce message ou un mandataire autorisé de celui-ci, vous 
êtes avisé par la présente que toute impression, diffusion, distribution ou 
reproduction de ce message et de tout fichier qui y est joint est 
strictement interdite. L'intégrité de ce message n'étant pas assurée sur 
Internet, IMEKA ne peut être tenue responsable de son contenu s'il a été 
altéré, déformé ou falsifié. Si ce message vous a été transmis par erreur, 
veuillez en aviser sans délai l'expéditeur et l'effacer ainsi que tout 
fichier joint sans en conserver de copie.
___
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users

Re: [mitk-users] PluginGenerator and ProjectTemplate

[Dinkelacker, Stefan]

Hi Nil,


spare the last step and do it already in the first step. Together with a few 
other little non-essential corrections like deactivating testing once instead 
of twice and relying on MITK Qt auto-detection since you installed Qt in its 
default location, your first CMake call (from anywhere) is then:


cmake -S C:/imeka/mitk -B C:/Imeka/mitk_build_5.12 -G "Visual Studio 16 2019" 
-D CMAKE_BUILD_TYPE:STRING=Release -D 
CMAKE_CONFIGURATION_TYPES:STRING="Debug;Release" -D BUILD_TESTING:BOOL=OFF -D 
MITK_EXTENSION_DIRS:STRING="C:/imeka/mibrain"


You could even spare most of the parameters and even the second call to CMake 
to configure the actual MITK-build when you add a 
"CMake/BuildConfigurations/mibrain.cmake" file to C:/imeka/mibrain/ where you 
transfer all your settings into (examples are in the same path in MITK). Then, 
all you would need to do is:


cmake -S C:/imeka/mitk -B C:/Imeka/mitk_build_5.12 -G "Visual Studio 16 2019" 
-D MITK_EXTENSION_DIRS:STRING="C:/imeka/mibrain" -D 
MITK_BUILD_CONFIGURATION:STRING="imeka"


That said, in your example, I cannot see why there should be a complete 
rebuild. In the last step, you do an MITK-superbuild after you did an 
MITK-build. Since some external projects are based on Git repositories instead 
of tarball downloads, at least these projects will generate build output again 
because of CMake-reasons but that should be more or less "Build project A, 
Update project A, (Yada yada is up-to-date) * n". And it should be done in a 
few seconds.


Best,

Stefan




Von: Nil Goyette 
Gesendet: Dienstag, 11. Mai 2021 17:45
An: Dinkelacker, Stefan
Cc: mitk-users@lists.sourceforge.net
Betreff: Re: [mitk-users] PluginGenerator and ProjectTemplate

Hi Stefan,

Sorry for the late reply, I'm not working on this project often. I didn't 
record a screencast but I took note of what I did. Maybe you will be able to 
spot what I did wrong.

# Install Qt 5.12.10 (QtScript, QtWebEngine, OpenSSL 1.1)
# Install CMake 3.19.7

# Create an empty extension project
mkdir C:\imeka
cd C:\imeka
mkdir C:\imeka\mibrain
mkdir C:\imeka\mibrain\Modules
Add a ModuleList.cmake file with an empty MITK_MODULES list
mkdir C:\imeka\mibrain\Plugins
Add a PluginList.cmake file with an empty MITK_PLUGINS list

# Get MITK
git clone https://phabricator.mitk.org/source/mitk.git
cd mitk
git checkout v2021.02

# Build MITK
cd ..
mkdir mitk_build_5.12
cd C:/Imeka/mitk_build_5.12
cmake -G "Visual Studio 16 2019" -DCMAKE_BUILD_TYPE:STRING=Release 
-DCMAKE_CONFIGURATION_TYPES:STRING="Debug;Release" -DBUILD_TESTING:BOOL=OFF 
-DQt5_DIR:PATH=C:/Qt/5.12.10/msvc2017_64/lib/cmake/Qt5 -DBUILD_TESTING:BOOL=0 
C:/Imeka/mitk/
Open the solution in Visual Studio and Build. Wait. Visual Studio tells me that 
everything has succeeded, nothing has failed.
== Génération : 20 a réussi, 0 a échoué, 0 à jour, 2 a été ignoré 
==
At that point, I can open the Workbench - About, and see ITK 4.13.3, VTK 9.0.1, 
Qt 5.12.10

# Add 2 plugins that we need (skipping this part still lead to a full MITK 
recompilation)
cd MITK-build
cmake -DMITK_BUILD_org.mitk.gui.qt.moviemaker:BOOL=ON 
-DMITK_BUILD_org.mitk.gui.qt.segmentation:BOOL=ON C:/Imeka/mitk/
Open the solution in Visual Studio and Build. Wait. Visual Studio tells me that 
everything has succeeded, nothing has failed.
== Génération : 18 a réussi, 0 a échoué, 2 à jour, 0 a été ignoré 
==
I can still open the Workbench and see the About dialog. And I see the 2 added 
plugins.
A rebuild (just for testing) in Visual Studio is fast, as expected, because 
it's doing nothing.

# Add our own projet (MITK extension)
cd ..
cmake -DMITK_EXTENSION_DIRS:PATH="C:/Imeka/mibrain" C:/Imeka/mitk/
Open the solution in Visual Studio and Build. Wait. Visual Studio tells me that 
everything has succeeded, nothing has failed.
But it's a complete MITK build again.

So, do you see anything obvious?

During this time of social distancing, we offer free webinars on subjects that 
matter.<https://www.imeka.ca/webinars/>
[https://www.imeka.ca/app/uploads/2021/03/logo-imeka-nom-10years-dark-fond-blanc-e1616690355918.png]
CONFIDENTIALITY NOTICE: This message, and any attachments, is intended only for 
the use of the addressee or his authorized representative. It may contain 
information that is privileged, confidential and exempt from disclosure under 
applicable law. If the reader of this message is not the intended recipient, or 
his authorized representative, you are hereby notified that any dissemination, 
distribution or copying of this message and any attachments is strictly 
prohibited. The integrity of this message cannot be guaranteed on the Internet, 
IMEKA shall not be liable for its content if altered, changed or falsified. If 
you have received this message in error, please contact immediately the sender 
and dele

Re: [mitk-users] PluginGenerator and ProjectTemplate

[Nil Goyette]

Hi Stefan,

Sorry for the late reply, I'm not working on this project often. I didn't
record a screencast but I took note of what I did. Maybe you will be able
to spot what I did wrong.

# Install Qt 5.12.10 (QtScript, QtWebEngine, OpenSSL 1.1)
# Install CMake 3.19.7

# Create an empty extension project
mkdir C:\imeka
cd C:\imeka
mkdir C:\imeka\mibrain
mkdir C:\imeka\mibrain\Modules
Add a ModuleList.cmake file with an empty MITK_MODULES list
mkdir C:\imeka\mibrain\Plugins
Add a PluginList.cmake file with an empty MITK_PLUGINS list

# Get MITK
git clone https://phabricator.mitk.org/source/mitk.git
cd mitk
git checkout v2021.02

# Build MITK
cd ..
mkdir mitk_build_5.12
cd C:/Imeka/mitk_build_5.12
cmake -G "Visual Studio 16 2019" -DCMAKE_BUILD_TYPE:STRING=Release
-DCMAKE_CONFIGURATION_TYPES:STRING="Debug;Release" -DBUILD_TESTING:BOOL=OFF
-DQt5_DIR:PATH=C:/Qt/5.12.10/msvc2017_64/lib/cmake/Qt5
-DBUILD_TESTING:BOOL=0 C:/Imeka/mitk/
Open the solution in Visual Studio and Build. Wait. Visual Studio tells me
that everything has succeeded, nothing has failed.
== Génération : 20 a réussi, 0 a échoué, 0 à jour, 2 a été ignoré
==
At that point, I can open the Workbench - About, and see ITK 4.13.3, VTK
9.0.1, Qt 5.12.10

# Add 2 plugins that we need (skipping this part still lead to a full MITK
recompilation)
cd MITK-build
cmake -DMITK_BUILD_org.mitk.gui.qt.moviemaker:BOOL=ON
-DMITK_BUILD_org.mitk.gui.qt.segmentation:BOOL=ON C:/Imeka/mitk/
Open the solution in Visual Studio and Build. Wait. Visual Studio tells me
that everything has succeeded, nothing has failed.
== Génération : 18 a réussi, 0 a échoué, 2 à jour, 0 a été ignoré
==
I can still open the Workbench and see the About dialog. And I see the 2
added plugins.
A rebuild (just for testing) in Visual Studio is fast, as expected, because
it's doing nothing.

# Add our own projet (MITK extension)
cd ..
cmake -DMITK_EXTENSION_DIRS:PATH="C:/Imeka/mibrain" C:/Imeka/mitk/
Open the solution in Visual Studio and Build. Wait. Visual Studio tells me
that everything has succeeded, nothing has failed.
*But it's a complete MITK build again. *

So, do you see anything obvious?

-- 
During this time of social distancing, we offer free webinars on subjects 
that matter. 

CONFIDENTIALITY NOTICE: This 
message, and any attachments, is intended only for the use of the addressee 
or his authorized representative. It may contain information that is 
privileged, confidential and exempt from disclosure under applicable law. 
If the reader of this message is not the intended recipient, or his 
authorized representative, you are hereby notified that any dissemination, 
distribution or copying of this message and any attachments is strictly 
prohibited. The integrity of this message cannot be guaranteed on the 
Internet, IMEKA shall not be liable for its content if altered, changed or 
falsified. If you have received this message in error, please contact 
immediately the sender and delete this message and any attachments from 
your system.


AVIS DE CONFIDENTIALITÉ : Ce message, ainsi que tout fichier 
qui y est joint, est destiné exclusivement aux personnes à qui il est 
adressé. Il peut contenir des informations de nature confidentielle qui ne 
doivent être divulguées en vertu des lois applicables. Si vous n'êtes pas 
le destinataire de ce message ou un mandataire autorisé de celui-ci, vous 
êtes avisé par la présente que toute impression, diffusion, distribution ou 
reproduction de ce message et de tout fichier qui y est joint est 
strictement interdite. L'intégrité de ce message n'étant pas assurée sur 
Internet, IMEKA ne peut être tenue responsable de son contenu s'il a été 
altéré, déformé ou falsifié. Si ce message vous a été transmis par erreur, 
veuillez en aviser sans délai l'expéditeur et l'effacer ainsi que tout 
fichier joint sans en conserver de copie.
___
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users

Re: [mitk-users] PluginGenerator and ProjectTemplate

[Dinkelacker, Stefan]

Hi Nil,


I really cannot reproduce your issues and looking at the CMake code I do not 
even see a possibility/code path that could lead to the behavior you describe. 
It is equivalent to saying "adding a new MITK module directly to MITK without 
any dependencies to other modules triggers a whole rebuild of MITK" or even 
"regenerating MITK in CMake without any modifications triggers a whole rebuild 
of MITK", it just doesn't make any sense to me. So I guess there must be a 
fundamental difference in how we understand the MITK extension feature. As it 
is hard to accurately describe what you do differently, it would help if you 
could maybe screen record your issue and show at the beginning, that the MITK 
solution was built successfully, before adding the extension?


(2) It's right though, that when adding modules or other stuff that you have to 
reconfigure/generate MITK which takes probably longer than just 
configuring/generating a completely separate project of course. Using MITK 
Whitelists can help here so that the build system only sees the modules you are 
actually using, instead of trying to build everything that's possible with the 
current set of satisfied dependencies.


(3) While MITK's own projects reside in the MITK root folder in Visual Studio, 
extensions reside in their own Visual Studio Solution root folder (see attached 
example screenshot)


(4) Again, a strong (third) indicator that there's something fundamentally 
different in your approach.


(5) I admit it is a bit hidden but there's CMake variables to tell MITK not to 
require "MITK" prefixes. For example, setting MITK_MODULE_NAME_PREFIX in your 
ModuleList.cmake will set another default prefix for modules then "Mitk". For 
plugins, you can set your own prefix template by adding something like the 
following to your PluginList.cmake: list(APPEND MITK_PLUGIN_REGEX_LIST 
"^org_imeka_[a-zA-Z0-9_]+$").


(6) The main motivation of all this is that there shouldn't be any pain points. 
:-) In particular you said that you are not used to CMake and writing new CMake 
files is a hurdle for you. That's a perfect reason to use the extension 
mechanism instead.


Fingers crossed

Stefan






Von: Nil Goyette 
Gesendet: Mittwoch, 21. April 2021 21:09
An: Dinkelacker, Stefan
Cc: mitk-users@lists.sourceforge.net
Betreff: Re: [mitk-users] PluginGenerator and ProjectTemplate

Hi Stefan,

Still no success. I deleted everything and started from a fresh build. Adding 
an "empty" project to  MITK_EXTENSION_DIRS does start a new MITK build. 
Removing it does the same thing. Once it's added, I can add modules and plugins 
without full compilation though. This being said, I see some problems with MITK 
extensions that I want to share with you:

  1.  This full recompilation problem is incompatible with our automated build 
system. I understand that it shouldn't happen, but it does happen.
  2.  Changing something in the extension (our project) takes much longer than 
usual because Visual Studio now checks the complete MITK project instead of our 
tiny project.
  3.  The Solution explorer only contains the MITK projects and dependencies.
  4.  Visual Studio doesn't seem to understand what's going on. There's no 
help, no intellisense, no nothing.
  5.  We must name our plugins "org.mitk.xyz<http://org.mitk.xyz>" otherwise 
cmake tells us that it's an invalid symbolic name. We already have our plugin 
names starting with org.imeka because we want to recognize them.
  6.  I didn't get further than that but I feel that there will be more 
pain-points. Possibly the branding (name and icon of the final application).

I think it's best if we avoid this extension feature., so I'll ask something 
new. Is there an up-to-date (2021.02) project that uses MITK as a library OR a 
minimal working example of such a thing?
I'm not used to cmake at all. I can modify existing cmake files but creating 
new ones for a new project is a big chore. Being able to read and copy such an 
exemple will greatly help me and probably some other users too.

During this time of social distancing, we offer free webinars on subjects that 
matter.<https://www.imeka.ca/webinars/>
[https://www.imeka.ca/app/uploads/2021/03/logo-imeka-nom-10years-dark-fond-blanc-e1616690355918.png]
CONFIDENTIALITY NOTICE: This message, and any attachments, is intended only for 
the use of the addressee or his authorized representative. It may contain 
information that is privileged, confidential and exempt from disclosure under 
applicable law. If the reader of this message is not the intended recipient, or 
his authorized representative, you are hereby notified that any dissemination, 
distribution or copying of this message and any attachments is strictly 
prohibited. The integrity of this message cannot be guaranteed on the Internet, 
IMEKA shall not be liable for its content if altered,

Re: [mitk-users] PluginGenerator and ProjectTemplate

[Nil Goyette]

Hi Stefan,

Still no success. I deleted everything and started from a fresh build.
Adding an "empty" project to  MITK_EXTENSION_DIRS does start a new MITK
build. Removing it does the same thing. Once it's added, I can add modules
and plugins without full compilation though. This being said, I see some
problems with MITK extensions that I want to share with you:

   1. This full recompilation problem is incompatible with our automated
   build system. I understand that it shouldn't happen, but it does happen.
   2. Changing something in the extension (our project) takes much longer
   than usual because Visual Studio now checks the complete MITK project
   instead of our tiny project.
   3. The Solution explorer only contains the MITK projects and
   dependencies.
   4. Visual Studio doesn't seem to understand what's going on. There's no
   help, no intellisense, no nothing.
   5. We must name our plugins "org.mitk.xyz" otherwise cmake tells us that
   it's an invalid symbolic name. We already have our plugin names starting
   with org.imeka because we want to recognize them.
   6. I didn't get further than that but I feel that there will be more
   pain-points. Possibly the branding (name and icon of the final application).

I think it's best if we avoid this extension feature., so I'll ask
something new. *Is there an up-to-date (2021.02) project that uses MITK as
a library OR a minimal working example of such a thing?*
I'm not used to cmake at all. I can modify existing cmake files but
creating new ones for a new project is a big chore. Being able to read and
copy such an exemple will greatly help me and probably some other users too.

-- 
During this time of social distancing, we offer free webinars on subjects 
that matter. 

CONFIDENTIALITY NOTICE: This 
message, and any attachments, is intended only for the use of the addressee 
or his authorized representative. It may contain information that is 
privileged, confidential and exempt from disclosure under applicable law. 
If the reader of this message is not the intended recipient, or his 
authorized representative, you are hereby notified that any dissemination, 
distribution or copying of this message and any attachments is strictly 
prohibited. The integrity of this message cannot be guaranteed on the 
Internet, IMEKA shall not be liable for its content if altered, changed or 
falsified. If you have received this message in error, please contact 
immediately the sender and delete this message and any attachments from 
your system.


AVIS DE CONFIDENTIALITÉ : Ce message, ainsi que tout fichier 
qui y est joint, est destiné exclusivement aux personnes à qui il est 
adressé. Il peut contenir des informations de nature confidentielle qui ne 
doivent être divulguées en vertu des lois applicables. Si vous n'êtes pas 
le destinataire de ce message ou un mandataire autorisé de celui-ci, vous 
êtes avisé par la présente que toute impression, diffusion, distribution ou 
reproduction de ce message et de tout fichier qui y est joint est 
strictement interdite. L'intégrité de ce message n'étant pas assurée sur 
Internet, IMEKA ne peut être tenue responsable de son contenu s'il a été 
altéré, déformé ou falsifié. Si ce message vous a été transmis par erreur, 
veuillez en aviser sans délai l'expéditeur et l'effacer ainsi que tout 
fichier joint sans en conserver de copie.
___
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users

Re: [mitk-users] PluginGenerator and ProjectTemplate

[Dinkelacker, Stefan]

Hi, yes I can confirm. If your build seems to start from scratch again, there's 
probably a difference to the prior build configuration in one of the core 
dependencies. Best, Stefan


Von: Nil Goyette 
Gesendet: Montag, 19. April 2021 20:18
An: Dinkelacker, Stefan
Cc: mitk-users@lists.sourceforge.net
Betreff: Re: [mitk-users] PluginGenerator and ProjectTemplate

Hi Stefan.

I'm currently testing the MITK extension. I created an almost empty project as 
you suggested . To be more specific, a "Modules" folder with an empty 
MITK_MODULES list, and a "Plugins" with an empty MITK_PLUGINS list. The simple 
fact of adding this extension to  MITK_EXTENSION_DIRS starts a full compilation 
again. There's no ITK, no dependencies, no nothing! Reading your last email, 
you seem to say that this full recompilation is not normal. Can you please 
confirm?

Nil

Le ven. 9 avr. 2021, à 04 h 49, Dinkelacker, Stefan 
mailto:s.dinkelac...@dkfz-heidelberg.de>> a 
écrit :

Hi,


the project template (or generally speaking an "MITK extension") can be built 
just like plain MITK, there is nothing extra or separate script/code paths in 
our build scripts. That's the cool thing about the project template/MITK 
extensions. It mirrors the MITK directory structure and all the magic happens 
within the MITK build system, not the project template build system. It 
basically works by following path and filename conventions. It is virtually 
like forking the MITK repository and adding dependencies, modules, plugins, 
applications, and build configurations right to the MITK repo, but with the 
advantage that you do not have to touch the original repo but have an extra 
directory/repo for your own stuff that is "mounted" into the MITK directory.


Notice that the project template is full of examples/demos that you do not need 
for your own stuff. Their purpose is to show how things are supposed to be done 
and that it is just like you would do stuff right in the MITK directory. One of 
the examples is that even the configurations of a few MITK-dependencies like 
ITK can be modified from an extension [1]. And this is why MITK was basically 
rebuilt completely when you added the ProjectTemplate itself to 
MITK_EXTENSION_DIRS since ITK as a core dependency needed a rebuild.


Since you already have all your stuff and just want to migrate, start with an 
empty directory instead of the project template and just use the project 
template as an example-based manual/inspiration.


For example, a minimum start could be to simple create a Modules folder, put a 
ModuleList.cmake in it and reference your first module [2]. That's all you need 
to add a module to MITK. When you then add your root directory to 
MITK_EXTENSION_DIRS (you can also do this in the MITK-build, not only in the 
MITK-superbuild as long as you do not change anything on superbuild-level), 
MITK will look for a Modules/ModuleList.cmake files not only in its own root 
directory but in all extension dirs and handle it just like its own 
Modules/ModuleList.cmake file.


Best,

Stefan


[1] 
https://github.com/MITK/MITK-ProjectTemplate/blob/master/CMakeExternals/Customization/ITK.cmake

[2] https://github.com/MITK/MITK-ProjectTemplate/tree/master/Modules



Von: Nil Goyette mailto:nil.goye...@imeka.ca>>
Gesendet: Freitag, 9. April 2021 04:19
An: Dinkelacker, Stefan
Cc: mitk-users@lists.sourceforge.net<mailto:mitk-users@lists.sourceforge.net>
Betreff: Re: [mitk-users] PluginGenerator and ProjectTemplate

Hi Stefan,
I'm still unable to generate the solution, with Qt5.12 or Qt5.15, with or 
without a reference to MitkAppUtil, with or without a 
"find_package(Qt5WebEngine REQUIRED)".. I get the same error as before.
This being said, I think I need to clarify the framework/library thing before 
we go further. If I understand correctly:

  *   MITK as a framework. Should use the ProjectTemplate and link to this 
template in the MITK superbuild.
  *   MITK as a library.. Use our own cmake and link to MITK build dir.

In our case, we use the standard MITK UI and features, we pick some useful MITK 
plugins and add some of our own. This is a "framework" usage, right? I tried 
the ProjectTemplate approach once and what I really disliked is that it 
recompiled MITK in full when I told cmake the MITK_EXTENSION_DIRS to my 
project. This is not compatible with our build system where we build MITK once 
and use the build artifacts to build our own project fast. Do you have a 
solution for this?
Nil

Le mer. 7 avr. 2021, à 06 h 59, Dinkelacker, Stefan 
mailto:s.dinkelac...@dkfz-heidelberg.de>> a 
écrit :

Hi,


my first guess is that your executable is infected with this dependency from 
MitkAppUtil, which has a PUBLIC package dependency to WebEngine. Usually CMake 
is right in its assumptions regarding find_package(). So a first step would be 
to do a man

Re: [mitk-users] PluginGenerator and ProjectTemplate

[Nil Goyette]

Hi Stefan.

I'm currently testing the MITK extension. I created an almost empty project
as you suggested . To be more specific, a "Modules" folder with an
empty MITK_MODULES list, and a "Plugins" with an empty MITK_PLUGINS list.
The simple fact of adding this extension to  MITK_EXTENSION_DIRS starts a
full compilation again. There's no ITK, no dependencies, no nothing!
Reading your last email, you seem to say that this full recompilation is
not normal. Can you please confirm?

Nil

Le ven. 9 avr. 2021, à 04 h 49, Dinkelacker, Stefan <
s.dinkelac...@dkfz-heidelberg.de> a écrit :

> Hi,
>
>
> the project template (or generally speaking an "MITK extension") can be
> built just like plain MITK, there is nothing extra or separate script/code
> paths in our build scripts. That's the cool thing about the project
> template/MITK extensions. It mirrors the MITK directory structure and all
> the magic happens within the MITK build system, not the project template
> build system. It basically works by following path and filename
> conventions. It is virtually like forking the MITK repository and adding
> dependencies, modules, plugins, applications, and build configurations
> right to the MITK repo, but with the advantage that you do not have to
> touch the original repo but have an extra directory/repo for your own stuff
> that is "mounted" into the MITK directory.
>
>
> Notice that the project template is full of examples/demos that you do not
> need for your own stuff. Their purpose is to show how things are supposed
> to be done and that it is just like you would do stuff right in the MITK
> directory. One of the examples is that even the configurations of a few
> MITK-dependencies like ITK can be modified from an extension [1]. And this
> is why MITK was basically rebuilt completely when you added the
> ProjectTemplate itself to MITK_EXTENSION_DIRS since ITK as a core
> dependency needed a rebuild.
>
>
> Since you already have all your stuff and just want to migrate, start with
> an empty directory instead of the project template and just use the project
> template as an example-based manual/inspiration.
>
>
> For example, a minimum start could be to simple create a Modules folder,
> put a ModuleList.cmake in it and reference your first module [2]. That's
> all you need to add a module to MITK. When you then add your root directory
> to MITK_EXTENSION_DIRS (you can also do this in the MITK-build, not only
> in the MITK-superbuild as long as you do not change anything on
> superbuild-level), MITK will look for a Modules/ModuleList.cmake files not
> only in its own root directory but in all extension dirs and handle it just
> like its own Modules/ModuleList.cmake file.
>
>
> Best,
>
> Stefan
>
>
> [1]
> https://github.com/MITK/MITK-ProjectTemplate/blob/master/CMakeExternals/Customization/ITK.cmake
>
> [2] https://github.com/MITK/MITK-ProjectTemplate/tree/master/Modules
>
>
> ------
> *Von:* Nil Goyette 
> *Gesendet:* Freitag, 9. April 2021 04:19
> *An:* Dinkelacker, Stefan
> *Cc:* mitk-users@lists.sourceforge.net
> *Betreff:* Re: [mitk-users] PluginGenerator and ProjectTemplate
>
> Hi Stefan,
> I'm still unable to generate the solution, with Qt5.12 or Qt5.15, with or
> without a reference to MitkAppUtil, with or without a
> "find_package(Qt5WebEngine REQUIRED)".. I get the same error as before.
> This being said, I think I need to clarify the framework/library thing
> before we go further. If I understand correctly:
>
>- MITK as a framework. Should use the ProjectTemplate and link to this
>template in the MITK superbuild.
>- MITK as a library.. Use our own cmake and link to MITK build dir.
>
> In our case, we use the standard MITK UI and features, we pick some useful
> MITK plugins and add some of our own. This is a "framework" usage, right? I
> tried the ProjectTemplate approach once and what I really disliked is that
> it recompiled MITK in full when I told cmake the MITK_EXTENSION_DIRS to
> my project. This is not compatible with our build system where we build
> MITK once and use the build artifacts to build our own project fast. Do you
> have a solution for this?
> Nil
>
> Le mer. 7 avr. 2021, à 06 h 59, Dinkelacker, Stefan <
> s.dinkelac...@dkfz-heidelberg.de> a écrit :
>
>> Hi,
>>
>>
>> my first guess is that your executable is infected with this dependency
>> from MitkAppUtil, which has a PUBLIC package dependency to WebEngine.
>> Usually CMake is right in its assumptions regarding find_package(). So a
>> first step would be to do a manual find_package for WebEngine and continue
>> from there. If i

Re: [mitk-users] PluginGenerator and ProjectTemplate

[Dinkelacker, Stefan]

Hi,


the project template (or generally speaking an "MITK extension") can be built 
just like plain MITK, there is nothing extra or separate script/code paths in 
our build scripts. That's the cool thing about the project template/MITK 
extensions. It mirrors the MITK directory structure and all the magic happens 
within the MITK build system, not the project template build system. It 
basically works by following path and filename conventions. It is virtually 
like forking the MITK repository and adding dependencies, modules, plugins, 
applications, and build configurations right to the MITK repo, but with the 
advantage that you do not have to touch the original repo but have an extra 
directory/repo for your own stuff that is "mounted" into the MITK directory.


Notice that the project template is full of examples/demos that you do not need 
for your own stuff. Their purpose is to show how things are supposed to be done 
and that it is just like you would do stuff right in the MITK directory. One of 
the examples is that even the configurations of a few MITK-dependencies like 
ITK can be modified from an extension [1]. And this is why MITK was basically 
rebuilt completely when you added the ProjectTemplate itself to 
MITK_EXTENSION_DIRS since ITK as a core dependency needed a rebuild.


Since you already have all your stuff and just want to migrate, start with an 
empty directory instead of the project template and just use the project 
template as an example-based manual/inspiration.


For example, a minimum start could be to simple create a Modules folder, put a 
ModuleList.cmake in it and reference your first module [2]. That's all you need 
to add a module to MITK. When you then add your root directory to 
MITK_EXTENSION_DIRS (you can also do this in the MITK-build, not only in the 
MITK-superbuild as long as you do not change anything on superbuild-level), 
MITK will look for a Modules/ModuleList.cmake files not only in its own root 
directory but in all extension dirs and handle it just like its own 
Modules/ModuleList.cmake file.


Best,

Stefan


[1] 
https://github.com/MITK/MITK-ProjectTemplate/blob/master/CMakeExternals/Customization/ITK.cmake

[2] https://github.com/MITK/MITK-ProjectTemplate/tree/master/Modules



Von: Nil Goyette 
Gesendet: Freitag, 9. April 2021 04:19
An: Dinkelacker, Stefan
Cc: mitk-users@lists.sourceforge.net
Betreff: Re: [mitk-users] PluginGenerator and ProjectTemplate

Hi Stefan,
I'm still unable to generate the solution, with Qt5.12 or Qt5.15, with or 
without a reference to MitkAppUtil, with or without a 
"find_package(Qt5WebEngine REQUIRED)".. I get the same error as before.
This being said, I think I need to clarify the framework/library thing before 
we go further. If I understand correctly:

  *   MITK as a framework. Should use the ProjectTemplate and link to this 
template in the MITK superbuild.
  *   MITK as a library.. Use our own cmake and link to MITK build dir.

In our case, we use the standard MITK UI and features, we pick some useful MITK 
plugins and add some of our own. This is a "framework" usage, right? I tried 
the ProjectTemplate approach once and what I really disliked is that it 
recompiled MITK in full when I told cmake the MITK_EXTENSION_DIRS to my 
project. This is not compatible with our build system where we build MITK once 
and use the build artifacts to build our own project fast. Do you have a 
solution for this?
Nil

Le mer. 7 avr. 2021, à 06 h 59, Dinkelacker, Stefan 
mailto:s.dinkelac...@dkfz-heidelberg.de>> a 
écrit :

Hi,


my first guess is that your executable is infected with this dependency from 
MitkAppUtil, which has a PUBLIC package dependency to WebEngine. Usually CMake 
is right in its assumptions regarding find_package(). So a first step would be 
to do a manual find_package for WebEngine and continue from there. If it still 
cannot be found, but other components of Qt were found, double-check your 
installation and maybe manually look for the Config.cmake file in the lib/cmake 
subfolder of your Qt installation. Since you seem to use MITK as library it is 
hard to make better guesses at the moment. I also did not use Qt 5.15 yet, only 
5.12.


Best,

Stefan


Von: Nil Goyette mailto:nil.goye...@imeka.ca>>
Gesendet: Dienstag, 6. April 2021 17:21
An: Dinkelacker, Stefan
Cc: mitk-users@lists.sourceforge.net<mailto:mitk-users@lists.sourceforge.net>
Betreff: Re: [mitk-users] PluginGenerator and ProjectTemplate

Hi Stefan,

My module wasn't found because I included "MitkTestingHelper" in the wrong 
place. There was no useful error message so I had to guess it.
But now I have another problem and you may be able to help me. The CMake 
Configure part is ok, but when I click on Generate, I get this error

CMake Error at 
C:/Imeka/mitk/CMake/mitkFunctionCreateBlueBerryApplication.cmake:88 

Re: [mitk-users] PluginGenerator and ProjectTemplate

[Nil Goyette]

Hi Stefan,
I'm still unable to generate the solution, with Qt5.12 or Qt5.15, with or
without a reference to MitkAppUtil, with or without a
"find_package(Qt5WebEngine REQUIRED)".. I get the same error as before.
This being said, I think I need to clarify the framework/library thing
before we go further. If I understand correctly:

   - MITK as a framework. Should use the ProjectTemplate and link to this
   template in the MITK superbuild.
   - MITK as a library.. Use our own cmake and link to MITK build dir.

In our case, we use the standard MITK UI and features, we pick some useful
MITK plugins and add some of our own. This is a "framework" usage, right? I
tried the ProjectTemplate approach once and what I really disliked is that
it recompiled MITK in full when I told cmake the MITK_EXTENSION_DIRS to my
project. This is not compatible with our build system where we build MITK
once and use the build artifacts to build our own project fast. Do you have
a solution for this?
Nil

Le mer. 7 avr. 2021, à 06 h 59, Dinkelacker, Stefan <
s.dinkelac...@dkfz-heidelberg.de> a écrit :

> Hi,
>
>
> my first guess is that your executable is infected with this dependency
> from MitkAppUtil, which has a PUBLIC package dependency to WebEngine.
> Usually CMake is right in its assumptions regarding find_package(). So a
> first step would be to do a manual find_package for WebEngine and continue
> from there. If it still cannot be found, but other components of Qt were
> found, double-check your installation and maybe manually look for the
> Config.cmake file in the lib/cmake subfolder of your Qt installation. Since
> you seem to use MITK as library it is hard to make better guesses at the
> moment. I also did not use Qt 5.15 yet, only 5.12.
>
>
> Best,
>
> Stefan
> --
> *Von:* Nil Goyette 
> *Gesendet:* Dienstag, 6. April 2021 17:21
> *An:* Dinkelacker, Stefan
> *Cc:* mitk-users@lists.sourceforge.net
> *Betreff:* Re: [mitk-users] PluginGenerator and ProjectTemplate
>
> Hi Stefan,
>
> My module wasn't found because I included "MitkTestingHelper" in the wrong
> place. There was no useful error message so I had to guess it.
> But now I have another problem and you may be able to help me. The CMake
> Configure part is ok, but when I click on Generate, I get this error
>
> CMake Error at
> C:/Imeka/mitk/CMake/mitkFunctionCreateBlueBerryApplication.cmake:88
> (add_executable):
> Target "MI-Brain" links to target "Qt5::WebEngine" but the target was not
> found. Perhaps a find_package() call is missing for an IMPORTED target, or
> an ALIAS target is missing?
> Call Stack (most recent call first):
> Apps/MI-Brain/CMakeLists.txt:34 (mitkFunctionCreateBlueBerryApplication)
> which is surprising because I don't use or try to include WebEngine. A git
> grep WebEngine returns nothing. And I know and verified that I installed
> WebEngine along with Qt 5.15.X. Do you know what is causing this?
>
> NIl
>
> Le lun. 5 avr. 2021, à 19 h 19, Dinkelacker, Stefan <
> s.dinkelac...@dkfz-heidelberg.de> a écrit :
>
>> Hi Nil,
>>
>>
>> you do *not* need to use the ProjectTemplate but it is at least the
>> strongly recommended way for new MITK developers to go the framework route
>> with MITK. You can still continue using MITK as plain
>> CMake-based toolkit/library. As written in T27701, we just want to get rid
>> of the ProjectGeneration part, not the PluginGeneration part.
>>
>>
>> We focus on the ProjectTemplate since we recognized that most of the
>> external developers are not primarily developers but scientists and while
>> they usually have at least a basic level of knowledge in C++ to get things
>> done, CMake is already something different. Using the ProjectTemplate
>> basically means using MITK as we do internally (which is a big plus for us
>> regarding support) and that people just need to add modules, plugins, or
>> dependencies to an existing application backed by examples/templates.
>>
>>
>> When a module is suddenly missing it is probably related to a missing
>> implicit dependency that is not there anymore (we revisited the ITK
>> dependencies of all MITK modules in v2021.02 for example). The CMake output
>> / summary should print out why a module is missing.
>>
>>
>> Best,
>>
>> Stefan
>>
>>
>>
>>
>>
>> --
>> *Von:* Nil Goyette 
>> *Gesendet:* Donnerstag, 1. April 2021 21:51
>> *An:* mitk-users@lists.sourceforge.net
>> *Betreff:* [mitk-users] PluginGenerator and ProjectTemplate
>>
>> Hi all,
>>
>> I tried porting my application t

Re: [mitk-users] PluginGenerator and ProjectTemplate

[Dinkelacker, Stefan]

Hi,


my first guess is that your executable is infected with this dependency from 
MitkAppUtil, which has a PUBLIC package dependency to WebEngine. Usually CMake 
is right in its assumptions regarding find_package(). So a first step would be 
to do a manual find_package for WebEngine and continue from there. If it still 
cannot be found, but other components of Qt were found, double-check your 
installation and maybe manually look for the Config.cmake file in the lib/cmake 
subfolder of your Qt installation. Since you seem to use MITK as library it is 
hard to make better guesses at the moment. I also did not use Qt 5.15 yet, only 
5.12.


Best,

Stefan


Von: Nil Goyette 
Gesendet: Dienstag, 6. April 2021 17:21
An: Dinkelacker, Stefan
Cc: mitk-users@lists.sourceforge.net
Betreff: Re: [mitk-users] PluginGenerator and ProjectTemplate

Hi Stefan,

My module wasn't found because I included "MitkTestingHelper" in the wrong 
place. There was no useful error message so I had to guess it.
But now I have another problem and you may be able to help me. The CMake 
Configure part is ok, but when I click on Generate, I get this error

CMake Error at 
C:/Imeka/mitk/CMake/mitkFunctionCreateBlueBerryApplication.cmake:88 
(add_executable):
Target "MI-Brain" links to target "Qt5::WebEngine" but the target was not
found. Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
Call Stack (most recent call first):
Apps/MI-Brain/CMakeLists.txt:34 (mitkFunctionCreateBlueBerryApplication)

which is surprising because I don't use or try to include WebEngine. A git grep 
WebEngine returns nothing. And I know and verified that I installed WebEngine 
along with Qt 5.15.X. Do you know what is causing this?

NIl

Le lun. 5 avr. 2021, à 19 h 19, Dinkelacker, Stefan 
mailto:s.dinkelac...@dkfz-heidelberg.de>> a 
écrit :

Hi Nil,


you do *not* need to use the ProjectTemplate but it is at least the strongly 
recommended way for new MITK developers to go the framework route with MITK. 
You can still continue using MITK as plain CMake-based toolkit/library. As 
written in T27701, we just want to get rid of the ProjectGeneration part, not 
the PluginGeneration part.


We focus on the ProjectTemplate since we recognized that most of the external 
developers are not primarily developers but scientists and while they usually 
have at least a basic level of knowledge in C++ to get things done, CMake is 
already something different. Using the ProjectTemplate basically means using 
MITK as we do internally (which is a big plus for us regarding support) and 
that people just need to add modules, plugins, or dependencies to an existing 
application backed by examples/templates.


When a module is suddenly missing it is probably related to a missing implicit 
dependency that is not there anymore (we revisited the ITK dependencies of all 
MITK modules in v2021.02 for example). The CMake output / summary should print 
out why a module is missing.


Best,

Stefan






Von: Nil Goyette mailto:nil.goye...@imeka.ca>>
Gesendet: Donnerstag, 1. April 2021 21:51
An: mitk-users@lists.sourceforge.net<mailto:mitk-users@lists.sourceforge.net>
Betreff: [mitk-users] PluginGenerator and ProjectTemplate

Hi all,

I tried porting my application to 2121.02 and there's plenty of cmake errors 
because one of my modules is suddenly missing. So I tried using the good old 
PluginGenerator, but  I see that there's a problem with it. It's not built when 
I build MITK. It was decided in T27701<https://phabricator.mitk.org/T27701> to 
get rid of it. I learned that there's a 
ProjectTemplate<https://phabricator.mitk.org/source/mitk-projecttemplate/>. Is 
the old method (our project linking to MITK_BUILD) not working anymore? Can you 
please confirm that we must now use this ProjectTemplate?
--
Nil Goyette
Développeur principal
www.imeka.ca<http://www.imeka.ca>

During this time of social distancing, we offer free webinars on subjects that 
matter.<https://www.imeka.ca/webinars/>
[https://www.imeka.ca/app/uploads/2021/03/logo-imeka-nom-10years-dark-fond-blanc-e1616690355918.png]
CONFIDENTIALITY NOTICE: This message, and any attachments, is intended only for 
the use of the addressee or his authorized representative. It may contain 
information that is privileged, confidential and exempt from disclosure under 
applicable law. If the reader of this message is not the intended recipient, or 
his authorized representative, you are hereby notified that any dissemination, 
distribution or copying of this message and any attachments is strictly 
prohibited. The integrity of this message cannot be guaranteed on the Internet, 
IMEKA shall not be liable for its content if altered, changed or falsified. If 
you have received this message in error, please contact immediately the sender 
and delete this message and 

Re: [mitk-users] PluginGenerator and ProjectTemplate

[Nil Goyette]

Hi Stefan,

My module wasn't found because I included "MitkTestingHelper" in the wrong
place. There was no useful error message so I had to guess it.
But now I have another problem and you may be able to help me. The CMake
Configure part is ok, but when I click on Generate, I get this error

CMake Error at
C:/Imeka/mitk/CMake/mitkFunctionCreateBlueBerryApplication.cmake:88
(add_executable):
Target "MI-Brain" links to target "Qt5::WebEngine" but the target was not
found. Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
Call Stack (most recent call first):
Apps/MI-Brain/CMakeLists.txt:34 (mitkFunctionCreateBlueBerryApplication)
which is surprising because I don't use or try to include WebEngine. A git
grep WebEngine returns nothing. And I know and verified that I installed
WebEngine along with Qt 5.15.X. Do you know what is causing this?

NIl

Le lun. 5 avr. 2021, à 19 h 19, Dinkelacker, Stefan <
s.dinkelac...@dkfz-heidelberg.de> a écrit :

> Hi Nil,
>
>
> you do *not* need to use the ProjectTemplate but it is at least the
> strongly recommended way for new MITK developers to go the framework route
> with MITK. You can still continue using MITK as plain
> CMake-based toolkit/library. As written in T27701, we just want to get rid
> of the ProjectGeneration part, not the PluginGeneration part.
>
>
> We focus on the ProjectTemplate since we recognized that most of the
> external developers are not primarily developers but scientists and while
> they usually have at least a basic level of knowledge in C++ to get things
> done, CMake is already something different. Using the ProjectTemplate
> basically means using MITK as we do internally (which is a big plus for us
> regarding support) and that people just need to add modules, plugins, or
> dependencies to an existing application backed by examples/templates.
>
>
> When a module is suddenly missing it is probably related to a missing
> implicit dependency that is not there anymore (we revisited the ITK
> dependencies of all MITK modules in v2021.02 for example). The CMake output
> / summary should print out why a module is missing.
>
>
> Best,
>
> Stefan
>
>
>
>
>
> ------
> *Von:* Nil Goyette 
> *Gesendet:* Donnerstag, 1. April 2021 21:51
> *An:* mitk-users@lists.sourceforge.net
> *Betreff:* [mitk-users] PluginGenerator and ProjectTemplate
>
> Hi all,
>
> I tried porting my application to 2121.02 and there's plenty of cmake
> errors because one of my modules is suddenly missing. So I tried using the
> good old PluginGenerator, but  I see that there's a problem with it. It's
> not built when I build MITK. It was decided in T27701
> <https://phabricator.mitk.org/T27701> to get rid of it. I learned that
> there's a ProjectTemplate
> <https://phabricator.mitk.org/source/mitk-projecttemplate/>. Is the old
> method (our project linking to MITK_BUILD) not working anymore? Can you
> please confirm that we must now use this ProjectTemplate?
> --
> Nil Goyette
> Développeur principal
> www.imeka.ca
>

-- 
During this time of social distancing, we offer free webinars on subjects 
that matter. <https://www.imeka.ca/webinars/>

CONFIDENTIALITY NOTICE: This 
message, and any attachments, is intended only for the use of the addressee 
or his authorized representative. It may contain information that is 
privileged, confidential and exempt from disclosure under applicable law. 
If the reader of this message is not the intended recipient, or his 
authorized representative, you are hereby notified that any dissemination, 
distribution or copying of this message and any attachments is strictly 
prohibited. The integrity of this message cannot be guaranteed on the 
Internet, IMEKA shall not be liable for its content if altered, changed or 
falsified. If you have received this message in error, please contact 
immediately the sender and delete this message and any attachments from 
your system.


AVIS DE CONFIDENTIALITÉ : Ce message, ainsi que tout fichier 
qui y est joint, est destiné exclusivement aux personnes à qui il est 
adressé. Il peut contenir des informations de nature confidentielle qui ne 
doivent être divulguées en vertu des lois applicables. Si vous n'êtes pas 
le destinataire de ce message ou un mandataire autorisé de celui-ci, vous 
êtes avisé par la présente que toute impression, diffusion, distribution ou 
reproduction de ce message et de tout fichier qui y est joint est 
strictement interdite. L'intégrité de ce message n'étant pas assurée sur 
Internet, IMEKA ne peut être tenue responsable de son contenu s'il a été 
altéré, déformé ou falsifié. Si ce message vous a été transmis par erreur, 
veuillez en aviser sans délai l'expéditeur et l'effacer ainsi que tout 
fichier joint sans en conserver de copie.
___
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users

Re: [mitk-users] PluginGenerator and ProjectTemplate

[Dinkelacker, Stefan]

Hi Nil,


you do *not* need to use the ProjectTemplate but it is at least the strongly 
recommended way for new MITK developers to go the framework route with MITK. 
You can still continue using MITK as plain CMake-based toolkit/library. As 
written in T27701, we just want to get rid of the ProjectGeneration part, not 
the PluginGeneration part.


We focus on the ProjectTemplate since we recognized that most of the external 
developers are not primarily developers but scientists and while they usually 
have at least a basic level of knowledge in C++ to get things done, CMake is 
already something different. Using the ProjectTemplate basically means using 
MITK as we do internally (which is a big plus for us regarding support) and 
that people just need to add modules, plugins, or dependencies to an existing 
application backed by examples/templates.


When a module is suddenly missing it is probably related to a missing implicit 
dependency that is not there anymore (we revisited the ITK dependencies of all 
MITK modules in v2021.02 for example). The CMake output / summary should print 
out why a module is missing.


Best,

Stefan






Von: Nil Goyette 
Gesendet: Donnerstag, 1. April 2021 21:51
An: mitk-users@lists.sourceforge.net
Betreff: [mitk-users] PluginGenerator and ProjectTemplate

Hi all,

I tried porting my application to 2121.02 and there's plenty of cmake errors 
because one of my modules is suddenly missing. So I tried using the good old 
PluginGenerator, but  I see that there's a problem with it. It's not built when 
I build MITK. It was decided in T27701<https://phabricator.mitk.org/T27701> to 
get rid of it. I learned that there's a 
ProjectTemplate<https://phabricator.mitk.org/source/mitk-projecttemplate/>. Is 
the old method (our project linking to MITK_BUILD) not working anymore? Can you 
please confirm that we must now use this ProjectTemplate?
--
Nil Goyette
Développeur principal
www.imeka.ca<http://www.imeka.ca>

During this time of social distancing, we offer free webinars on subjects that 
matter.<https://www.imeka.ca/webinars/>
[https://www.imeka.ca/app/uploads/2021/03/logo-imeka-nom-10years-dark-fond-blanc-e1616690355918.png]
CONFIDENTIALITY NOTICE: This message, and any attachments, is intended only for 
the use of the addressee or his authorized representative. It may contain 
information that is privileged, confidential and exempt from disclosure under 
applicable law. If the reader of this message is not the intended recipient, or 
his authorized representative, you are hereby notified that any dissemination, 
distribution or copying of this message and any attachments is strictly 
prohibited. The integrity of this message cannot be guaranteed on the Internet, 
IMEKA shall not be liable for its content if altered, changed or falsified. If 
you have received this message in error, please contact immediately the sender 
and delete this message and any attachments from your system.


AVIS DE CONFIDENTIALITÉ : Ce message, ainsi que tout fichier qui y est joint, 
est destiné exclusivement aux personnes à qui il est adressé. Il peut contenir 
des informations de nature confidentielle qui ne doivent être divulguées en 
vertu des lois applicables. Si vous n'êtes pas le destinataire de ce message ou 
un mandataire autorisé de celui-ci, vous êtes avisé par la présente que toute 
impression, diffusion, distribution ou reproduction de ce message et de tout 
fichier qui y est joint est strictement interdite. L'intégrité de ce message 
n'étant pas assurée sur Internet, IMEKA ne peut être tenue responsable de son 
contenu s'il a été altéré, déformé ou falsifié. Si ce message vous a été 
transmis par erreur, veuillez en aviser sans délai l'expéditeur et l'effacer 
ainsi que tout fichier joint sans en conserver de copie.
___
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users

[mitk-users] PluginGenerator and ProjectTemplate

[Nil Goyette]

Hi all,

I tried porting my application to 2121.02 and there's plenty of cmake
errors because one of my modules is suddenly missing. So I tried using the
good old PluginGenerator, but  I see that there's a problem with it. It's
not built when I build MITK. It was decided in T27701
 to get rid of it. I learned that
there's a ProjectTemplate
. Is the old
method (our project linking to MITK_BUILD) not working anymore? Can you
please confirm that we must now use this ProjectTemplate?
-- 
Nil Goyette
Développeur principal
www.imeka.ca

-- 
During this time of social distancing, we offer free webinars on subjects 
that matter. 

CONFIDENTIALITY NOTICE: This 
message, and any attachments, is intended only for the use of the addressee 
or his authorized representative. It may contain information that is 
privileged, confidential and exempt from disclosure under applicable law. 
If the reader of this message is not the intended recipient, or his 
authorized representative, you are hereby notified that any dissemination, 
distribution or copying of this message and any attachments is strictly 
prohibited. The integrity of this message cannot be guaranteed on the 
Internet, IMEKA shall not be liable for its content if altered, changed or 
falsified. If you have received this message in error, please contact 
immediately the sender and delete this message and any attachments from 
your system.


AVIS DE CONFIDENTIALITÉ : Ce message, ainsi que tout fichier 
qui y est joint, est destiné exclusivement aux personnes à qui il est 
adressé. Il peut contenir des informations de nature confidentielle qui ne 
doivent être divulguées en vertu des lois applicables. Si vous n'êtes pas 
le destinataire de ce message ou un mandataire autorisé de celui-ci, vous 
êtes avisé par la présente que toute impression, diffusion, distribution ou 
reproduction de ce message et de tout fichier qui y est joint est 
strictement interdite. L'intégrité de ce message n'étant pas assurée sur 
Internet, IMEKA ne peut être tenue responsable de son contenu s'il a été 
altéré, déformé ou falsifié. Si ce message vous a été transmis par erreur, 
veuillez en aviser sans délai l'expéditeur et l'effacer ainsi que tout 
fichier joint sans en conserver de copie.
___
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users