Hello José,

it is the plugin name. CTK requires all project plugin names to follow specific 
rules and these rules can be overridden my defining a macro named 
GetMyTargetLibraries. We do this in our top-level CMakeLists.txt (see [1]). The 
plugin names must start with org.mitk. or org.blueberry.

It is quite strict indeed but for now you have two options: change the rules in 
your copy of MITK, or go with org.mitk.kcl… until we made these rules less 
strict (I’ll create a task for this for 2018.04.4 which has no schedule yet).

BTW, there’s already something related for modules, see [2].

Best,
Stefan

[1] 
https://github.com/MITK/MITK/blob/3c9b6ff72d1232496cc9afc1147fa1787111b96b/CMakeLists.txt#L1133-L1139

[2] https://phabricator.mitk.org/T24167#122363
From: José Alonso Solís Lemus [mailto:alonso.jasl+...@gmail.com]
Sent: Wednesday, April 17, 2019 1:51 PM
To: mitk-users@lists.sourceforge.net
Subject: [mitk-users] [Migrating to MITK v2018.04.2] Invalid Plugin Names Error

Dear MITK developers,

We are in the process of migrating our application from v2016.03 to v2018.04.2, 
following the external project template. The migration process has been 
relatively straightforwrd, however we have encountered a particular problem 
with our plugins, we get the error:

CMake Error at 
/path/to/mitk-build/ep/src/CTK/CMake/ctkMacroSetupPlugins.cmake:154 (message):
  The following plug-ins are using invalid symbolic names: (plugin names)

For context, I will try provide as much detail of what we have done to address 
this issue. Note that we are using different plugin names, e.g. 
kcl.cemrgapp.testplugin; which we are not entirely sure we can use. Anyway, our 
approach to this was:

1. We made sure all the names are consistent throughout all the files in all 
the plugins. No luck.
2. On the example plugins, we noticed a different name in the PluginActivator.h 
and .cpp files. We changed this as well without luck.
3. We tried to create a test plugin with the MitkPluginGenerator binary in 
another clean MITK build with the following command:
./MitkPluginGenerator -ps kcl.cemrgapp.testplugin -vn "Test Plugin" -v KCL -o 
/some/path/
Then changed the resulting folder to our project file and added the plugin's 
name to our PluginList.cmake file. However not even the test plugin was 
recognised.

We hope you can help us, because at this point we ran out of ideas. We are 
happy to provide more information if you require it.

Kind regards,
José Alonso





_______________________________________________
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to