New package: goldendict-ng-LiXia.240505
Testing the changes
- I tested the changes in this PR: YES
New package
- This new package conforms to the package requirements: YES
Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC) x86_64-glibc
Please use the established conventions for the commit message.
@classabbyamp can you activate the workflow?
Is there a way I can run the linter on my local machine?
xlint in the xtools package
Hi!
I'm trying to cross-build the package for aarch64 and I'm able to get past the Qt6HostInfo error message (now it gets detected automatically, but you can also pass -DQt6HostInfo_DIR=/usr/aarch64-linux-gnu/usr/lib/cmake/Qt6HostInfo to cmake. However, the following error message pops up:
/usr/aarch64-linux-gnu/usr/lib64/qt6/libexec/qmlimportscanner: /usr/aarch64-linux-gnu/usr/lib64/qt6/libexec/qmlimportscanner: cannot execute binary file CMake Error at /usr/aarch64-linux-gnu/usr/lib64/cmake/Qt6Qml/Qt6QmlMacros.cmake:3361 (message): Failed to scan target goldendict-ng for QML imports: 126 Call Stack (most recent call first): /usr/aarch64-linux-gnu/usr/lib64/cmake/Qt6Qml/Qt6QmlMacros.cmake:3403 (_qt_internal_scan_qml_imports) /usr/aarch64-linux-gnu/usr/lib64/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (qt6_import_qml_plugins) /usr/aarch64-linux-gnu/usr/lib64/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (cmake_language) /usr/aarch64-linux-gnu/usr/lib64/cmake/Qt6Core/Qt6CoreMacros.cmake:774 (_qt_internal_finalize_executable) /usr/aarch64-linux-gnu/usr/lib64/cmake/Qt6Core/Qt6CoreMacros.cmake:590:EVAL:1 (qt6_finalize_target) CMakeLists.txt:DEFERRED
Running file on the aforementioned binary reveals the following:
masterdir-x86_64/usr/aarch64-linux-gnu/usr/lib64/qt6/libexec/qmlimportscanner: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, BuildID[sha1]=35f93a674a89578308260dfaf9839cb6816dce9d, for GNU/Linux 3.7.0, stripped
I believe qt6-declarative-tools may be relevant here. Perhaps somebody will have a clue what's going on here and whether and how this could be fixed.
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.