View Single Post
Old 06-23-2024, 06:56 AM   #20
orontee
Connoisseur
orontee ought to be getting tired of karma fortunes by now.orontee ought to be getting tired of karma fortunes by now.orontee ought to be getting tired of karma fortunes by now.orontee ought to be getting tired of karma fortunes by now.orontee ought to be getting tired of karma fortunes by now.orontee ought to be getting tired of karma fortunes by now.orontee ought to be getting tired of karma fortunes by now.orontee ought to be getting tired of karma fortunes by now.orontee ought to be getting tired of karma fortunes by now.orontee ought to be getting tired of karma fortunes by now.orontee ought to be getting tired of karma fortunes by now.
 
orontee's Avatar
 
Posts: 85
Karma: 250308
Join Date: Sep 2023
Location: Toulouse, France
Device: Vivlio Touch HD Plus, reMarkable Paper Pro
News on a PocketBook port of Gargoyle

Last version of the SDK includes Qt (see https://www.mobileread.com/forums/sh...d.php?t=361705), so now it should be possible to build Qt applications. (@Biep Qt5 libraries being installed on devices is not sufficient to build an application that depends on Qt5; It's only a requirement. In previous versions of the SDK, the build stuff for Qt apps was missing).

I thus decided to give up writing a pure "Inkview" front-end based and started to work on a mostly unchanged build of Gargoyle.

Detailed instructions to cross-compile garglk dependencies and try to build garglk itself are available in gargoyle-pocketbook-port Github project.

For dependencies it now looks good. But the built gargoyle contains hard-coded paths, the path to fonts and the path to interpreter. So at present time it fails to run any interpreter.

Remarks
  • Sound support is disabled at build time since it adds a dependency on SDL2
  • No idea what keyboard support we'll have once the paths are fixed...
  • My knowledge of CMake is limited, and fixing the hard-coded paths problem is certainly trivial if one uses CMake procedure to install the application
  • Harfbuzz and Freetype2 are complex libraries so don't expect things to work seamlessly after the hard-coded paths are fixed

Last edited by orontee; 06-23-2024 at 10:39 AM. Reason: News update
orontee is offline   Reply With Quote