-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DLT 2.25.0 won't launch #398
Comments
In case someone else is having the issue, for now I've fixed it by symlinking the library in
|
@bunty95 Please close ticket if issue is solved. |
It worked! |
issue is resolved. |
Works with Apple M1 Pro and Sonoma 14.3.1 |
Issue still needs to be addressed in the latest master build. |
Issue is fixed with latest push #482 |
Using the provided "DLT-macOS.zip" and running the DLTViewer program, below is the error that is found.
Seems like the build/packaging is not done correctly.
Possibly due to QT5 being used to build instead of QT6?
Process: dlt-viewer [8447]
Path: /Volumes/VOLUME/*/DLTViewer.app/Contents/MacOS/dlt-viewer
Identifier: org.genivi.dlt-viewer
Version: 2.25.0 (2.25.0)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2023-12-14 11:29:43.1041 -0500
OS Version: macOS 12.7.1 (21G920)
Report Version: 12
Bridge OS Version: 3.0 (14Y910)
Anonymous UUID: 90FE766C-B1B7-0302-5C3A-F87C84E24D45
Sleep/Wake UUID: 9C9C233B-7A95-4937-849A-9CA4F48277AF
Time Awake Since Boot: 68000 seconds
Time Since Wake: 283 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace DYLD, Code 1 Library missing
Library not loaded: '@rpath/libqdlt.dylib'
Referenced from: '/Volumes/VOLUME/*/DLTViewer.app/Contents/MacOS/dlt-viewer'
Reason: tried: '' (no such file), '' (no such file), '' (no such file), '' (no such file), '' (no such file), '' (no such file)
(terminated at launch; ignore backtrace)
The text was updated successfully, but these errors were encountered: