My provisioning files are:

main project:
--->
READ file:///<{REMOVED}>/vc9_x64/bin/ExtApp.provisioning

START file:///<{REMOVED}>/vc9_x64/bin/libehtz_isosurface.dll
START file:///<{REMOVED}>/vc9_x64/bin/libethz_automaticsegmentation.dll
START file:///<{REMOVED}>/vc9_x64/bin/libethz_basicimageprocessing.dll
START file:///<{REMOVED}>/vc9_x64/bin/libethz_entropyfilter.dll
                    .
                                   .
                                   .
START file:///<{REMOVED}>/vc9_x64/bin/libethz_simpletransform.dll
START file:///<{REMOVED}>/vc9_x64/bin/libethz_perspective.dll
<---

ExtApp.provisioning:
<----
READ file://<{REMOVED}>/vc9_x64/bin/BlueBerry.provisioning

START file://<{REMOVED}>/vc9_x64/bin/plugins/liborg_mitk_core_services.dll
START file://<{REMOVED}>/vc9_x64/bin/plugins/liborg_mitk_gui_common.dll
START file://<{REMOVED}>/vc9_x64/bin/plugins/liborg_mitk_gui_qt_common.dll
START 
file://<{REMOVED}>/vc9_x64/bin/plugins/liborg_mitk_gui_qt_application.dll
START file://<{REMOVED}>/vc9_x64/bin/plugins/liborg_mitk_core_ext.dll
START file://<{REMOVED}>/vc9_x64/bin/plugins/liborg_mitk_planarfigure.dll
START file://<{REMOVED}>/vc9_x64/bin/plugins/liborg_mitk_gui_qt_ext.dll
START 
file://<{REMOVED}>/vc9_x64/bin/plugins/liborg_mitk_gui_qt_extapplication.dll
START 
file://<{REMOVED}>/vc9_x64/bin/plugins/liborg_mitk_gui_qt_datamanager.dll
START 
file://<{REMOVED}>/vc9_x64/bin/plugins/liborg_mitk_gui_qt_colourimageprocessing.dll
START 
file://<{REMOVED}>/vc9_x64/bin/plugins/liborg_mitk_gui_qt_imagenavigator.dll
START 
file://<{REMOVED}>/vc9_x64/bin/plugins/liborg_mitk_gui_qt_imagestatistics.dll
START 
file://<{REMOVED}>/vc9_x64/bin/plugins/liborg_mitk_gui_qt_materialeditor.dll
START 
file://<{REMOVED}>/vc9_x64/bin/plugins/liborg_mitk_gui_qt_imagecropper.dll
START 
file://<{REMOVED}>/vc9_x64/bin/plugins/liborg_mitk_gui_qt_volumevisualization.dll
--->

BlueBerry.provisioning:
--->
START file:///<{REMOVED}>/vc9_x64/bin/plugins/liborg_blueberry_osgi.dll
START file:///<{REMOVED}>/vc9_x64/bin/plugins/liborg_blueberry_compat.dll
START 
file:///<{REMOVED}>/vc9_x64/bin/plugins/liborg_blueberry_core_runtime.dll
START 
file:///<{REMOVED}>/vc9_x64/bin/plugins/liborg_blueberry_core_expressions.dll
START 
file:///<{REMOVED}>/vc9_x64/bin/plugins/liborg_blueberry_solstice_common.dll
START 
file:///<{REMOVED}>/vc9_x64/bin/plugins/liborg_blueberry_core_commands.dll
START file:///<{REMOVED}>/vc9_x64/bin/plugins/liborg_blueberry_ui.dll
START file:///<{REMOVED}>/vc9_x64/bin/plugins/liborg_blueberry_ui_qt.dll
START file:///<{REMOVED}>/vc9_x64/bin/plugins/liborg_blueberry_ui_qt_log.dll
<---

Looking into solstice,ini, ExtApp.ini and my main project's .ini, i see 
that /bin/BlueBerry and /bin/ExtBundles are listed, but not created 
during make. Is this relevant? As i didnt change anything in the MITK 
makefile I take it uses its own paths without interference. Comparing it 
to a standalone 32bit superbuild the files seem to be identical.

Note that all plugins are created in the ./bin/plugins subdirectory, and 
copied afterwards to ./bin (so that visual studio can run without batch 
files).

Regards,
Thomas

------------------------------------------------------------------------------
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-d2d-oct
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to