Hi Marija, Caspar,
I suspect Caspar is on the right track here, as this rings a distant dull
sounding bell.
Firstly, that printout that looks like it comes from the batch script is
normally a red herring. This stuff:
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: The command "setlocal
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: cd C:\CRIMSON\sb\CRIMSON-build
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: if %errorlevel% neq 0 goto :cmEnd
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: C:
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: if %errorlevel% neq 0 goto :cmEnd
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: "C:\Program Files (x86)\Cmake3.5\bin\cpack.exe" -C Release --config
./CPackConfig.cmake
gets printed whenever the packaging fails. If the packaging fails it normally
fails when finding additional dependencies.
So, I’m seeing, that you are including Python in your installer. The python
console plugin depends on a Modules/Python and this module autoloads
PythonService. This PythonService microservice will depend on the actual python
library which is compiled as an external project. I suspect that the process
that recursively finds all .dlls required for a complete package therefore does
not do dependency resolution for python correctly.
So,
1. As Caspar suggests, do a standard MITK release build with Python OFF. This
should work.
2. Then do a build of your project with Python OFF. If python is the issue,
then this should work.
3. Then, run dependency walker on the python plugin, python module,
PythonService and work out which one of these requires linking at runtime to
the python dll. Then find where your python library is compiled, and add this
path to MITK_ADDITIONAL_LIBRARY_SEARCH_PATHS to try and see if the dependencies
can all be resolved.
or if you are in a hurry, just try step 3 :-)
Hope that helps.
M
On 9 Jan 2018, at 09:06, Goch, Caspar Jonas
<[email protected]<mailto:[email protected]>> wrote:
Hi Marija,
does it work if you disable Python? We do not usually include it in our binary
releases and that seems to be the main difference as far as I can see.
Best,
Caspar
Von: Marija Marcan [mailto:[email protected]]
Gesendet: Montag, 8. Januar 2018 17:34
An: [email protected]<mailto:[email protected]>
Betreff: [mitk-users] Packaging problem since migration to MITK 2016.11
Hello all,
I am working on a project which is based on MITK, though a bit modified version
of it (changes in some modules + matplotlib external dependency for MITK). Up
to version 2016.03 integration, building and packaging of everything was
running smoothly.
I've recently integrated the MITK 2016.11 into our repository and both the MITK
and our project build and run fine. The problem occurs with the packaging,
though. While trying to run PACKAGE on our project it would successfully copy
all the plugin .dlls but fail to do the same for the external dependencies of
MITK. The output log wasn't very helpful:
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: The command "setlocal
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: cd C:\CRIMSON\sb\CRIMSON-build
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: if %errorlevel% neq 0 goto :cmEnd
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: C:
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: if %errorlevel% neq 0 goto :cmEnd
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: "C:\Program Files (x86)\Cmake3.5\bin\cpack.exe" -C Release --config
./CPackConfig.cmake
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: if %errorlevel% neq 0 goto :cmEnd
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: :cmEnd
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: :cmErrorLevel
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: exit /b %1
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: :cmDone
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: if %errorlevel% neq 0 goto :VCEnd
1>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error
MSB3073: :VCEnd" exited with code -1073740791.
After this error, I have tried to run PACKAGE on our version of MITK-build and
it, too broke with a bit different output (in packageErrorLog.txt).
Things became even more cryptic after I tried to run the PACKAGE on the MITK
2016.11 master version. The error output I got was similar to the one above
(attached below in packageErrorLogMITK.txt).
I know this is probably a long shot, but I was wondering if anyone here had
encountered a similar issue? Or if anyone has an idea how I might get more info
from these error logs? Searching for the code -1073740791 brought no results.
I'm currently using Cmake 3.5.2, VS 2013 and Qt 5.7.
Thank you for your time,
Marija
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org<http://Slashdot.org>!
http://sdm.link/slashdot_______________________________________________
mitk-users mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/mitk-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
