Hi Matt,
quickly looking at the stack trace I see that the application somehow
dragged in both libMitk.dylib and libMitkCore.dylib where only
libMitkCore.dylib should exist. It also references version 1.99 as well
as version 2.99 of libCppMicroServies.dylib at the same time. The "Mitk"
module was recently renamed to "MitkCore". So this is probably not
related to MacOS... can you remove all binary artefacts from your build
tree in MITK-build/bin and try again please? Make sure that there is no
libMitk.dylib or any old CppMicroServices reference any more.
Best,
Sascha
On 03/04/2014 11:34 AM, Clarkson, Matt wrote:
HI All,
thanks for help so far. My point is that I need to know that the make
package actually works. So that I can install an application on a
separate machine, and use it without it crashing, without any
work-arounds. At the moment, I cannot do this. So, building yesterdays
MITK master, on Mavericks, using 10.8 SDK, libstdc++, with a Qt
compiled against this I a stack trace which is attached along with the
otool -L output.
So, either I am building it wrong, or the default MITK master does not
work on Mavericks.
What do you think? How am I supposed to build and install on
Mavericks? This question is just pertaining to the standard
mitkWorkbench, not our application.
Thanks
Matt
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
