MobileRead Forums - View Single Post - kobo-reader sdk installation buged on WSL2

NiLuJe · 07-24-2021, 09:25 AM

That script is essentially stuck in the olden days of the Kobo OG and/or Kobo Touch. Don't use it.

TL;DR:

* If you actually intend to work with the *stock* Qt & QPA, use NickelTC (or build a Dockerless version of it from my scripts, c.f., https://github.com/pgaskin/NickelTC/issues/2 where we just discussed something like that). I'd link to my binaries for this, but, IIRC, the final one is the *sole* file that got eaten by the dreaded OVH fire

.
* If you don't, use koxtoolchain & the kobo target. Possibly with a custom Qt5 build & QPA (c.f., UMR & InkBox) if you *really* want new Qt.

So, a good start would be asking *what*, exactly, you're intending to do?

07-24-2021, 09:25 AM	#2
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	That script is essentially stuck in the olden days of the Kobo OG and/or Kobo Touch. Don't use it. TL;DR: * If you actually intend to work with the stock Qt & QPA, use NickelTC (or build a Dockerless version of it from my scripts, c.f., https://github.com/pgaskin/NickelTC/issues/2 where we just discussed something like that). I'd link to my binaries for this, but, IIRC, the final one is the sole file that got eaten by the dreaded OVH fire . * If you don't, use koxtoolchain & the kobo target. Possibly with a custom Qt5 build & QPA (c.f., UMR & InkBox) if you really want new Qt. So, a good start would be asking what, exactly, you're intending to do? Last edited by NiLuJe; 07-24-2021 at 09:34 AM.