Page MenuHomePhabricator

VTK bin PATH is missing in startmitkWorkbench_release/debug.bat
Closed, ResolvedPublic

Description

Hi

when building the newest MITK release from git, the path to the VTK bin directory is missing in the startmitkWorkbench_release.bat, startmitkWorkbench_debug.bat files.

The error is not comprehensible due to a plugin loading problem message:
release\mitkWorkbench.exe
Wed Dec 11 11:36:55 2013
0.08 blueberry.osgi.intPltfm ERROR: ctkPluginException: Failed to install plugin
at 000007FEF39C2E50: ??0ctkBackTrace@@QEAA@_K@Z + 0x80
at 000007FEF39D83D2: ??0ctkException@@QEAA@AEBVQString@@AEBV0@@Z + 0x42
at 000007FEF39D86BE: ??0ctkRuntimeException@@QEAA@AEBVQString@@AEBVctkException@@@Z + 0xe
at 000007FEF3A39219: ??0ctkPluginException@@QEAA@AEBVQString@@AEBW4Type@0@AEBVctkException@@@Z + 0x19
at 000007FEF3A67268: ?metaObject@ctkTrackedServiceListener@@UEBAPEBUQMetaObject@@XZ + 0x7288
at 0000000072888A40: __unDNameEx + 0xabc
at 0000000072880463: ?_is_exception_typeof@@YAHAEBVtype_info@@PEAU_EXCEPTION_POINTERS@@@Z + 0x1bf
at 0000000077BA0C51: RtlRestoreContext + 0x2e2
at 000007FEF3A4BF69: ?getLocale@ctkPluginLocalization@@QEBA?AVQLocale@@XZ + 0x5a89
at 000007FEF3A382C8: ?installPlugin@ctkPluginContext@@QEAA?AV?$QSharedPointer@VctkPlugin@@@@AEBVQUrl@@PEAVQIODevice@@@Z + 0x48
at 000007FEFB7CF698: ?Initialize@InternalPlatform@berry@@QEAAXAEAHPEAPEADPEAVAbstractConfiguration@Util@Poco@@@Z + 0x1df8
at 000007FEFB7BAD10: ?Run@Starter@berry@@SAHAEAHPEAPEADPEAVAbstractConfiguration@Util@Poco@@@Z + 0xd0
at 000000013F772492: ???
at 000000013F774C12: ???
at 0000000077A4652D: BaseThreadInitThunk + 0xd
at 0000000077B7C541: RtlUserThreadStart + 0x21
Caused by: ctkPluginException: The plugin "D:/Libraries/MITK3/Build/MITK-build/bin/plugins/Release/liborg_mitk_core_services.dll" could not be loaded: Cannot load library D:/Libraries/MITK3/Build/MITK-build/bin/plugins/Release/liborg_mitk_core_services.dll: The specified module could not be found.
at 000007FEF39C2E50: ??0ctkBackTrace@@QEAA@_K@Z + 0x80
at 000007FEF39D833A: ??0ctkException@@QEAA@AEBVQString@@@Z + 0x3a
at 000007FEF39D868E: ??0ctkRuntimeException@@QEAA@AEBVQString@@@Z + 0xe
at 000007FEF3A391D6: ??0ctkPluginException@@QEAA@AEBVQString@@AEBW4Type@0@@Z + 0x16
at 000007FEF3A50021: ?getLocale@ctkPluginLocalization@@QEBA?AVQLocale@@XZ + 0x9b41
at 000007FEF3A51940: ?getLocale@ctkPluginLocalization@@QEBA?AVQLocale@@XZ + 0xb460
at 000007FEF3A53461: ?getLocale@ctkPluginLocalization@@QEBA?AVQLocale@@XZ + 0xcf81
... 8 more

etc.

Event Timeline

With the current vtk version this bug is fixed.