Hi There,
just an update, so, it's documented on the mailing list.
So, we were struggling to get our external project running on Windows. This was
mainly caused by creating our project before the MITK-project-template was
ready, so we had produced our own CMake, as we also have other things to build.
Things to check were:
1. Make sure StartVS.bat.in got generated correctly for both Debug and Release
builds, so it can be used to launch Visual Studio with correct path to debug
app.
2. We had ITK and VTK building, AND INSTALLING which was wrong. The install
folder doesn't contain Debug and Release directory path. So, the app compiles,
but at runtime doesn't load all the libraries, so plugins are reported as being
"not found", when in reality, the plugin was found, it was the subsequent
dependencies that were not found.
3. If you have added additional libraries, they may need the folder containing
the library adding to StartVS.bat.in and StartAppName.bat.in
4. Some of our code needing to be tweaked for Windows (e.g. calling ITK code,
from MITK had to be in the same class, you couldnt have the templated ITK code
in a base class).
I think that was about it.
So, thanks everybody.
Matt
On 8 Sep 2011, at 14:18, Sascha Zelzer wrote:
Hi,
On 09/07/2011 03:49 PM, Clarkson, Matt wrote:
1.) As a developer, I compile everything in Debug mode, then using
StartVS_Debug.bat to launch Visual Studio, i should be able to launch the
application directly from within Visual Studio for debugging purposes. I don't
need to run the startApplication_Debug/Release.bat file to launch my
application as Visual Studio already has the correct path, so Visual Studio
should run the binary directly.
Yes, completely correct.
2.) When it comes to a full "make install" or "make package", then I HAVE to
be in Release mode, and the final application thats generated should be
launched using the startApplication_Release.bat file?
The first part (about Release mode) is correct, but the installed/packaged
application should be launchable by double-clicking on its .exe file. There
also should not be startApplication_Release.bat file in the installation folder.
Since all libraries which are needed by the .exe file are copied into the same
folder as the .exe file during packaging/installation, Windows will find the
library dependencies by itself (it first looks in the application path).
Best,
Sascha
Thanks
Matt
On 7 Sep 2011, at 14:34, Sascha Zelzer wrote:
Hi Matt,
The provisioning files intentionally leave out the intermediate output
directory. During the plugin install process, the plugin is looked for in
different subdirectories. If it does not exist in ".../bin/", it is searched in
".../bin/CMAKE_INT_DIR/" where CMAKE_INT_DIR is a compiler define set to the
build type used when building MITK.
So maybe you have built MITK in Release mode, but your app in Debug mode?
Best,
Sascha
On 09/06/2011 07:09 PM, Clarkson, Matt wrote:
Hi there,
(apologies for all the emails today).
I am just trying to run our external application on Windows. The application
compiles, but when I run the startMyApp_releast.bat file I get the following
errors:
2.56 blueberry.osgi.intPltfm ERROR: Failed to install:
file:///C:/build/UCLToolkit-SuperbuildRelease/MITK-build/MITK-build/bin/plugins/Release/liborg_mitk_core_services.dll,
Failed to install plugin: The plugin could not be loaded:
C:/build/UCLToolkit-SuperbuildRelease/MITK-build/MITK-build/bin/plugins/Release/liborg_mitk_core_services.dll
Caused by: Cannot load library
C:/build/UCLToolkit-SuperbuildRelease/MITK-build/MITK-build/bin/plugins/Release/liborg_mitk_core_services.dll:
The specified module could not be found.
Caused by: Cannot load library
C:/build/UCLToolkit-SuperbuildRelease/MITK-build/MITK-build/bin/plugins/Release/liborg_mitk_core_services.dll:
The specified module could not be found.
Caused by: The plugin could not be loaded:
C:/build/UCLToolkit-SuperbuildRelease/MITK-build/MITK-build/bin/plugins/Release/liborg_mitk_core_services.dll
Caused by: Cannot load library
C:/build/UCLToolkit-SuperbuildRelease/MITK-build/MITK-build/bin/plugins/Release/liborg_mitk_core_services.dll:
The specified module could not be found.
Caused by: Cannot load library
C:/build/UCLToolkit-SuperbuildRelease/MITK-build/MITK-build/bin/plugins/Release/liborg_mitk_core_services.dll:
The specified module could not be found.
I did just notice that the application provisioning file seems to miss the
Release folder in the names of the plugins.
So, we have lines like this:
START
file:///C:/build/UCLToolkit-SuperbuildRelease/UCLToolkit-build/bin/plugins
/libuk_ac_ucl_cmic_gui_qt_common.dll
which does not exist on my C drive instead of this (which is more in line with
what I would expect).
START
file:///C:/build/UCLToolkit-SuperbuildRelease/UCLToolkit-build/bin/plugins/Release/libuk_ac_ucl_cmic_gui_qt_common.dll
Then I went and checked what the ExtApp.provisioning file contains and it also
contains lines like this:
START
file:///C:/build/UCLToolkit-SuperbuildRelease/MITK-build/MITK-build/bin/plugins/liborg_mitk_core_services.dll
which is wrong, and should probably be:
START
file:///C:/build/UCLToolkit-SuperbuildRelease/MITK-build/MITK-build/bin/plugins/Release/liborg_mitk_core_services.dll
However, the paths in the error message appears to be CORRECT. So the error
message appears correct, and the provisioning file appears wrong.
Is there anything obvious Im missing?
Any help would be greatfully appreciated.
Thanks as always.
Matt
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
