Hi, as I wrote in my first reply to Stefans email, you should never (!) do this. Having the same export/import macro names in different shared libraries will lead to troubles when you start to include header files from each other. See me previous email for a solution how to deal with that.
Best, Sascha On 06/28/2010 08:19 AM, Bryn Lloyd wrote: > Hi, > > I am not a visual studio expert, but I think this kind of macro is used > to export objects or functions from a DLL. For instance in mitkCommon.h > there are macros like this: > > #define MITK_CORE_EXPORT __declspec(dllexport) > > so maybe you should define the macro as: > > #define MITKEXT_CORE_EXPORT __declspec(dllexport) > > Cheers > Bryn > > > > > Stefan Galowicz wrote: > >> Hello dear list! >> >> I'm currently trying to port an MITK plugin of a former co-worker to >> MITK-SVN, but when I load it at runtime (click its symbol) I get a >> widget with the error >> >> You can find the code >> here: http://github.com/funkybit/mitk-imageregistration >> >> "Unable to create view ID org.mitk.views.imageregistration >> Part initialization error: Node is already in DataStorage >> - Check your shared library for unresolved symbols >> - Check your class attribute in your plugin.xml file" >> Check your manifest.cp file" >> >> My plugin.xml seems to be correct: >> <?xml version="1.0" encoding="UTF-8"?> >> <?BlueBerry version="0.1"?> >> <plugin> >> >> <extension point="org.blueberry.ui.views"> >> <view id="org.mitk.views.imageregistration" >> name="ImageRegistration" >> class="::QmitkImageRegistrationView" >> icon="resources/icon.xpm" /> >> </extension> >> >> </plugin> >> >> I have a class called QmitkImageRegistrationView, too. >> In my view's .cpp file it says const std::string >> QmitkImageRegistrationView::VIEW_ID = "org.mitk.views.imageregistration"; >> >> The file manifest.cpp uses >> POCO_EXPORT_CLASS(::QmitkImageRegistratinView), which matches my class. >> >> Dependency walker can find every DLL apart from 2 non-critical windows 7 >> DLLs (error reporting DLL wer.dll for example, don't remember the >> other), after adding the DLL search paths. E.g.: >> >> class MITKEXT_CORE_EXPORT BaseRegistration : public ImageToImageFilter >> >> That macro isn't defined for me while building in Visual Studio C++ >> 2008. So I simply did >> >> #include "mitkImageRegistrationMacros.h" >> #ifndef MITKEXT_CORE_EXPORT >> #define MITKEXT_CORE_EXPORT >> #endif >> >> >> Could that have broken anything? I've never seen this macro before either. >> >> Thanks for your help! >> >> Sincerely, >> Stefan >> >> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------------ >> ThinkGeek and WIRED's GeekDad team up for the Ultimate >> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >> lucky parental unit. See the prize list and enter to win: >> http://p.sf.net/sfu/thinkgeek-promo >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> mitk-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/mitk-users >> > > ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
