Hi Dora,
I am not sure if my comments are still valid because I haven't used MITK
much recently. Back then, "make package" was not supposed to be used for
debug builds. It would work for some special cases, but not in general
if I remember correctly.
The first thing I would check is if your release package references the
correct set of shared libraries (dylib files). I am not familiar with
Xcode (if you happen to use it), but you should be able to see the list
of loaded dylib files when running your executable with the Xcode
debugger attached.
Things to watch out for:
1. Do you have a mix of release and debug dylibs loaded?
2. Are the loaded Qt libraries of the same (or newer) version as the
ones you originally linked with?
Regarding Qt, its libraries may or may not be packaged when you run
"make package", depending on their install location.
Best,
Sascha
On 06/14/2017 04:05 PM, Admin Uniapp wrote:
Hi again,
Can anybody help me with this please? I understand that building in
debug mode may in some cases hides semantic errors in the code but I
can't see anything in the place where the application crashes. Does
anyone have experience of packaging in OSX?
Any hints is highly appreciated as this has given me a headache for
the last week or so.
Many thanks
Dora
On Mon, Jun 12, 2017 at 4:04 PM, Admin Uniapp <contactuni...@gmail.com
<mailto:contactuni...@gmail.com>> wrote:
Hello all,
I've been having numerous problems with creating a package of my
MITK project since the new OSX updates:
- First I had to add CMAKE_INSTALL_RPATH to point it to where VMTK
libraries are in the MITK build directory, otherwise make package
would complain about not finding VMTK libraries
- Setting the project build type to release builds and makes a
package but for a very strange reason when I test the application
it crashes after running a few operations. I know there is nothing
wrong with the operations because they work fine on linux and also
the application crashes when it reaches the end of a function
where there is no interesting code:
...
this->BusyCursorOn();
mitk::ProgressBar::GetInstance()->AddStepsToDo(1);
std::unique_ptr<CommandLine> cmd(new CommandLine());
cmd->ExecuteCreateMesh(directory, templatePath);
QMessageBox::information(NULL, "Attention",
"Command Line Operations Finished!");
this->BusyCursorOff();
//Code runs fine up to here and the suddenly
crashes after the message box!
} else if(dialogCode == QDialog::Rejected) {
inputs->close();
inputs->deleteLater();
}//_if
} catch(mitk::Exception& e) {
return;
}//_try
} else
return;
} else
return;
- More confusing is when I set the build type to debug, the crash
I explained in the last point does not happen but trying to make
package from debug mode fails with errors like this:
CMake Error at
/Users/dxr/Install/Proj-build/Apps/ProjApp/cmake_install.cmake:452
(file):
file INSTALL cannot find
"/Users/dxr/Install/Projapp/Apps/ProjApp/_target_loc_debug-NOTFOUND".
Call Stack (most recent call first):
/Users/dxr/Install/Proj-build/Apps/cmake_install.cmake:32 (include)
/Users/dxr/Install/Proj-build/cmake_install.cmake:78 (include)
Can someone please help a little with these? I have run out of
things to try and not really sure what's going on!
Many thanks
Dora
------------------------------------------------------------------------------
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
mitk-users@lists.sourceforge.net
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
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users
