Hi Rachit,
US_NAMESPACE is just a #define. It was already present in the last release but
resolved to "mitk". Now it resolves to "us", hence you can simply use the nice
and short latter one instead of US_NAMESPACE.
Regarding UnWindows.h it seems that _WIN32_WINNT was already defined to a value
lower than 0x0501. If this wasn't done by Poco it might have been done by ITK
(itkThreadSupport.h 0x0400) or VTK (vtkConditionVariable.h 0x0500). If one of
these two guesses is right, rearranging headers in your project might help.
Best,
Stefan
Von: Rachit Jain [mailto:[email protected]]
Gesendet: Donnerstag, 10. Oktober 2013 10:30
An: [email protected]
Betreff: [mitk-users] Migration from MITK version 2013.06.0 to MITK version
2013.09.0
Hi All
Came to know about new MITK version 2013.09.0, so was curious to try and use it.
My application (C++ using VS2010, QT 4.8.4 on windows 7 64 bit) was using MITK
2013.06.0 and while moving to version 2013.09.0, I got some minor issues that I
fixed, so sharing with all of you so that everybody can take benefit out of it:
1. The path of CppMicroServices is changed from
Core/Code/CppMicroServices/include to Core/CppMicroServices/include
2. Because of new QWT version 6.1.0, classes like QwtIntervalData,
QwtDoubleRect do not exist anymore. So refactoring is required. This link might
be helpful: http://www.qtcentre.org/archive/index.php/t-49691.html
3. Header files have been changed from mitkModuleRegistry.h to
usModuleRegistry.h. Similarly Module and ModuleRegistry classes are not in mitk
namespace anymore, they are in US_NAMESPACE namespace.
There is one issue which I am not able to fix yet, i.e. related to UnWindows.h,
I see a section that says:
#if defined(_WIN32_WINNT) && (_WIN32_WINNT < 0x0501)
#error Unsupported Windows version.
#elif !defined(_WIN32_WINNT)
// define minimum supported
#define _WIN32_WINNT 0x0501
#endif
When I am building my application, it gives me a compilation error saying
"Unsupported Windows version". I commented the #error, just for testing
purpose, then my application compiles but fails to run. I searched in Cmake
settings of MITK, but could not find anything specific related to this.
Please share if you have encountered the same issue or know how to fix it.
Thanks and Regards
Rachit Jain
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
