Hi Ghazall,
the plug-ins available at runtime for a specific application are defined
in the <your-app-name>.provisioning file (located in your project's bin
directory). The provisioning file must contain an entry to the
org.mitk.gui.qt.common plug-in (or point to a file containing such an
entry). The provisioning file itself is referenced either in the
<your-app-name>.ini file (if it exists) or by specifying an application
property in <your-app-name>.cpp (the .ini file takes precedence).
Could you please check these points?
Thanks,
Sascha
On 12/20/2011 01:58 PM, Ghazall Aghaei wrote:
Hi list,
I went through the joy of updating MITK superbuild once again and this
time MITK built all fine and dandy (thanks for fixing the recent
problems there)
Yet running my own-built plugins (recompiled against the new MITK)
outputs the following error in the MITK console:
blueberry.osgi.bundleloader ERROR: Bundle resolve failed: Cannot
resolve bundle: The bundle de.iccas.tumoroperator depends on missing
bundle:: org.mitk.gui.qt.common
I've checked via CMake in the MITK-build directory that
"mitk.gui.qt.common" is actually built and I've also read through
Sascha's last week's mail "Recent changes in MITK" but my
CMakeCache.txt did not contain any "CTK_PLUGIN_LIBRARIES" entry.
Any ideas?
Ghazall
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
