Be Ing (1b62b882) at 13 Feb 16:10
enable desktop OpenGL on aarch64
the pine64 should be able to run Desktop OpenGL without issue, thats a device specific bug if it is not working.
The Pinephone has a Mali 400 GPU which is supported by Mesa's Lima driver. According to the driver documentation:
Lima mainly targets OpenGL ES 2.0, as well as OpenGL 2.1 (desktop) to some extent.
The OpenGL (desktop) implementation is enabled by Mesa and Gallium, where it is possible to reuse the same implementation backend. That way, it is possible to support running a majority of Linux desktop applications designed for OpenGL. It is not possible to fully support OpenGL (desktop), though, due to hardware limitations. Some (but not all) features of OpenGL 2.1 that are not supported directly in hardware are enabled by internal shader transformations. Check the known hardware limitations list for additional information.
OpenGL ES 1.1 and OpenGL 1.x are also provided by Mesa and similarly supported to some extent in Lima.
So it seems building with -opengl es
isn't needed for the Pinephone's sake.
The Pinephone Pro has a Mali T860MP4 supported by Mesa's Panfrost driver. According to the driver documentation, it supports OpenGL 3.1 and OpenGL ES 3.1.
Thanks for catching and fixing this.
Be Ing (18479ef3) at 24 Jun 10:16
Merge? Android Qt 5.15 build failure looks unrelated:
CMake Warning at CMakeLists.txt:7 (find_package):
Could not find a configuration file for package "ECM" that is compatible
with requested version "5.95.0".
The following configuration files were considered but not accepted:
/opt/nativetooling/share/ECM/toolchain/../cmake/ECMConfig.cmake, version: 5.93.0
--
* ECM (required version >= 5.95.0), Extra CMake Modules., <https://commits.kde.org/extra-cmake-modules>
CMake Error at /opt/cmake/share/cmake-3.19/Modules/FeatureSummary.cmake:457 (message):
feature_summary() Error: REQUIRED package(s) are missing, aborting CMake
run.
Call Stack (most recent call first):
CMakeLists.txt:9 (feature_summary)
There is no Bugzilla ticket for this. I stumbled over an issue where application code was checking if the StorageAccess
returned by Solid::Device::storageAccessFromPath
was writable. When the path passed to Solid::Device::storageAccessFromPath
was on a LUKS encrypted drive, the application code failed to identify the StorageAccess
as writable because the return value from storageAccessFromPath
returned the StorageAccess
for the encrypted LUKS device rather than the device-mapped decrypted device.
otherwise storageAccessFromPath may return an encrypted LUKS device rather than its decrypted device-mapped counterpart
Be Ing (15cea82a) at 07 Jun 16:43
skip non-FileSystem StorageVolumes in storageAccessFromPath
... and 1 more commit
URIs are used in several other places in the portal API. Do those need to be fixed too?
An alternative to make it a setting could be requiring an extra step (click/press) to see it. This would discourage compulsively looking at it while still making the information available.
Maybe one day I'll revive this project as a new application using SixtyFPS with the same libsignal-service library that Whisperfish is using. But at the moment I think working on getting Whisperfish working with Kirigami is more practical.
The Whisperfish repository on GitHub is just a mirror. The canonical repository is on GitLab: https://gitlab.com/whisperfish/whisperfish/
Yes, I have abandoned the idea of Flare in favor of getting Whisperfish running without Sailfish OS. Unfortunately I haven't had a lot of time to work on Whisperfish, but someone else has made progress getting it running on Ubuntu Touch: https://gitlab.com/whisperfish/whisperfish/-/merge_requests/208
The requirement for KF5Wayland was raised by 4aa1bc3a which requires https://invent.kde.org/frameworks/kwayland/-/merge_requests/43 which was first released in KF5Wayland 5.86.
Be Ing (e978157d) at 11 Oct 18:03
CMake: raise KDE Frameworks minimum required version to 5.86