View Single Post
Old 04-15-2023, 06:28 PM   #5
luketheduke
Connoisseur
luketheduke knows what's going on.luketheduke knows what's going on.luketheduke knows what's going on.luketheduke knows what's going on.luketheduke knows what's going on.luketheduke knows what's going on.luketheduke knows what's going on.luketheduke knows what's going on.luketheduke knows what's going on.luketheduke knows what's going on.luketheduke knows what's going on.
 
luketheduke's Avatar
 
Posts: 87
Karma: 25608
Join Date: Sep 2022
Device: PW3, PW2, KT2, 2xKT, 2xK3G
Quote:
Originally Posted by NiLuJe View Post
You're trying to build a GTK-2 something. The toolchain doesn't know anything about GTK, it only provides you a compiler, a libc and kernel headers.

Now, Kindles *do* ship some god awful ancient bits of GTK stuff, so you *could* frankenstein something, but it's going to be a PITA unless you know what you're doing (specifically, you're going to need matching headers for the binaries shipped. You might want to look at the lab126 source code drop for your specifric FW release, I would imagine they'd be in there, in source form, at least, so you're not out of the woods yet ;p).

----

If you're aiming for GTK stuff, it might be easier to dig up whatever KTerm was using to be built, I imagine it's described somewhere.
Good to know. Unfortunately, I have no idea what I'm doing, so I'm going to see about the latter option.

Thanks for the info.

EDIT:

So I need to build GTK and its dependencies using the toolchain first?

EDIT:

NVM, I'm going to start with following KTerm's build instructions.

Last edited by luketheduke; 04-15-2023 at 06:46 PM.
luketheduke is offline   Reply With Quote