Quote:
Originally Posted by sherman
I bring this up, because I'm pretty sure that Nickel uses Qt (please correct me if I'm wrong!), and I would in no way be surprised if ACCESS also uses Qt (on the Kobo at least - I assume the underlying engine is not tied to any specific UI toolkit)
|
libnickel.so.1.0.0 depends on a lot of libQt5:
- libssl.so.1.0.0
- libcrypto.so.1.0.0
- libQtSolutions_IOCompressor-2.3.so.1
- libzip.so.1
- libxml2.so.2
- libxslt.so.1
- liblz4.so.1
- librmsdk.so.1
- libQt5WebKitWidgets.so.5
- libQt5MultimediaWidgets.so.5
- libQt5Svg.so.5
- libQt5PrintSupport.so.5
- libQt5Multimedia.so.5
- libQt5WebKit.so.5
- libQt5Widgets.so.5
- libQt5Concurrent.so.5
- libQt5Sensors.so.5
- libQt5Xml.so.5
- libQt5Sql.so.5
- libQt5DBus.so.5
- libQt5Script.so.5
- libQt5Network.so.5
- libQt5Gui.so.5
- libQt5Core.so.5
- libpng16.so.16
- libjpeg.so.62
- libicuuc.so.46
- libicudata.so.46
- libicui18n.so.46
- libdbus-1.so.3
- libdl.so.2
- librt.so.1
- libz.so.1
- libpthread.so.0
- libstdc++.so.6
- libm.so.6
- libgcc_s.so.1
- libc.so.6
- ld-linux-armhf.so.3
Nothing else font-ish stands out - except librmsdk? - so I think your assumption is good.