Difference between revisions of "Fixing external projects"

From mitk.org
Jump to navigation Jump to search
Line 47: Line 47:
 
myApp.setOrganizationName("My Organization");
 
myApp.setOrganizationName("My Organization");
 
</nowiki></pre>
 
</nowiki></pre>
 +
 +
 +
* Usually, your external project contains also [[BlueBerry]] bundles. You must fix them by following the instructions provided [[Fixing legacy BlueBerry bundles|here]].

Revision as of 10:52, 2 June 2011

If you generated a MITK project using the BundleGenerator, your projects build system probably needs a couple of tweaks to work with the new CTK-based BlueBerry.

  • Your custom executable needs a different set of include directories. The new variables to use are:
INCLUDE_DIRECTORIES(
  ${org_blueberry_osgi_INCLUDE_DIRS}
  ${Poco_INCLUDE_DIRS}
  ${mbilog_INCLUDE_DIRS}
)
  • The TARGET_LINK_LIBRARIES command for your executable should now look like
TARGET_LINK_LIBRARIES(<executable-target> org_blueberry_osgi)


  • Your applications .ini file needs an additional entry:
BlueBerry.provisioning=@MITK_PLUGIN_PROVISIONING_FILE@


  • Your executables .cpp file usually contains a statement like
#include <org.blueberry.osgi/src/application/berryStarter.h>
  • which must be changed to
#include <berryStarter.h>


  • Further, your executables .cpp file must now create a QApplication instance. So add the include directive "#include <QApplication>" and add the following lines at the beginning of your main method:
// Create a QApplication instance first
QApplication myApp(argc, argv);
myApp.setApplicationName("MyApp");
myApp.setOrganizationName("My Organization");


  • Usually, your external project contains also BlueBerry bundles. You must fix them by following the instructions provided here.