View Single Post
Old 05-21-2020, 06:53 PM   #2
sherman
Guru
sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.
 
Posts: 876
Karma: 2676800
Join Date: Aug 2008
Location: Taranaki - NZ
Device: Kobo Aura H2O, Kobo Forma
If you want to go C/C++, you have a couple of options for toolchains. You can use the koxtoolchain to setup a relatively newish GCC (7.x I believe) compiler toolchain on a linux system.

Another option is NickelTC, which is a dockerized toolchain that attempts to closely match the official Kobo toolchain and libraries, and includes a full sysroot for stuff like Qt libraries. It's an old GCC however (4.9).

If you want to use Rust, check out Plato by baskerville for an idea on what can be done.

My own Kobo UNCaGED demonstrates Go on the Kobo.

For displaying stuff to the screen, check out FBInk by NiLuJe.

If you want to see what can be done by integrating with Kobo's main binary (Nickel), check out NickelMenu by geek1011.

NiLuJe also has a package which bundles python, if you want to go that route.

In short, there are plenty of development options available for you to choose from. Pick your poison

EDIT: For whatever you end up doing, touch input and framebuffer handling are going to be the most annoying things to handle. Framebuffer stuff is handled by the afore-mentioned FBInk, but touch input....

Last edited by sherman; 05-21-2020 at 06:57 PM.
sherman is offline   Reply With Quote