Closed tcurdt closed 5 years ago
So it's failing to load the QtOpenGL library. Does CAMotics start at all?
Any more info on this?
Sorry, I didn't see the first comment.
Yes, it starts up, shows the main windows and then the crash report comes up. Given the main window stays alive I assume it must me some other process/executable that fails.
Let me know if I can help to debug this further.
A screenshot would be helpful I'm interested to know if you seen any 3D graphics in the application or if it's blank. It could be that the QtOpenGL
library is included and working but it is incorrectly linked to tplang
which shouldn't need it.
These are the libraries that are being used:
$ otool -L tplang
tplang:
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 104.1.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1226.10.1)
/usr/lib/libsqlite3.dylib (compatibility version 9.0.0, current version 216.4.0)
/usr/lib/libexpat.1.dylib (compatibility version 7.0.0, current version 8.0.0)
/usr/lib/libbz2.1.0.dylib (compatibility version 1.0.0, current version 1.0.5)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
/System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1258.1.0)
/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 728.13.0)
QtOpenGL.framework/Versions/4/QtOpenGL (compatibility version 4.8.0, current version 4.8.6)
QtGui.framework/Versions/4/QtGui (compatibility version 4.8.0, current version 4.8.6)
QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.6)
and this is how it looks like:
So there are some 3D graphics.
Ok, tplang
is linked to the Qt libraries, which it does not need to be, and it's having a problem loading QtOpenGL.framework/Versions/4/QtOpenGL
even though camotics
must be loading this fine since it is able to display 3D graphics. Looks like I need to release a new build that does not link the command line tools to the Qt libraries.
Thanks for making this application availiable.
I am running macOS on old Macbook built 2009 (patched for running this Version macOS 10.12.4 on older Hardware).
Systemversion: macOS 10.12.4 (16E195) Kernel-Version: Darwin 16.5.0
When starting the application via opening sample file box.tpl, the following message shows up in the lower window half.
dyld: Library not loaded: QtOpenGL.framework/Versions/4/QtOpenGL Referenced from: /Applications/CAMotics.app/Contents/MacOS/tplang Reason: Incompatible library version: tplang requires version 4.8.0 or later, but QtOpenGL provides version 4.5.0 Computing surface bounded by ((-32.8482,-2.77031,-13.4909), (32.8482,110.77,0.79092)) at 0.714092 grid resolution Time: 3.91 secs Triangles: 72616 Triangles/sec: 18579.76
while when opening a .nc file the (like the aztec calendar sample ) the calculation seems to be running without message regarding QtOpenGL.
Tool Path bounds ((-202.115,-202.489,-12.8854), (201.882,202.311,20.32)) dimensions (403.997,404.8,33.2054) Computing surface bounded by ((-203.75,-203.75,-15.715), (203.75,203.75,4.285)) at 0.5 grid resolution Time: 2 mins 14 secs Triangles: 7118228 Triangles/sec: 53039.79
Thanks for considering.
I'm hitting the same error running tplang on OS X, camotics runs fine for me. Looks like the release 1.1.1 on 2017-02-08 is still the latest, so I thought I'd see if I can build from source. Then see if I can eliminate the QT dependency. Currently I'm getting stuck building cbang. Here's the first of a couple related errors:
src/cbang/event/PersistentEventManager.cpp:40:14: error: 'Event' is not a class, namespace, or enumeration SmartPointer<Event::Event>
Which is strange since Event.h is included. My C++ is pretty rusty so any help would be great.
@zrichmond, this really should have been reported as a separate issue since it's only vaguely related. However, did the change I just checked into cbang fix this problem?
@jcoffland Fixed, thanks. Yeah sorry about the cross commenting, I know better too.
@zrichmond glad to hear it.
Any news on this?
I ended up battling compile errors with CAMotics on OS X which I wasn't able to nail down into an issue. So, I didn't get into working on a fix yet...
I'm working on a new release which should fix this problem.
Fixed in upcoming v1.2.0 release.
Fresh install on 10.12.3 (16D32) gives this on startup: