Build scripts to help generate cross ToolChains for various platforms supported by KOReader.

• git
• ncurses
• gperf
• help2man
• bison
• texinfo
• flex
• gawk
• unzip

sudo pacman -S base-devel curl git gperf help2man unzip wget

sudo apt-get install build-essential autoconf automake bison flex gawk libtool libtool-bin libncurses-dev curl file git gperf help2man texinfo unzip wget

The build script takes a platform name as its first argument. For example, to build a cross toolchain for legacy non-touch kindle devices, type:

./gen-tc.sh kindle

You can use ./gen-tc.sh -h to get a list of supported platforms.

After the build is finished, you should be able to find your cross ToolChains under the ~/x-tools directory.

The reference script can be used to automatically setup a cross-compilation environment (PATH, *FLAGS & all that jazz), as mentioned at the end of a TC build.
For example, for a Kobo TC:

source refs/x-compile.sh kobo env

Due to a whole lot of legacy baggage, the names of the various Kindle TCs may be slightly confusing (especially compared to KOReader's target names), so, let's disambiguate that:

No such worries on Kobo & Cervantes, though ;).

The nickel TC is a Kobo variant that mimics Kobo's own TC (as of FW >= 4.6). It is not recommended for general purpose stuff, only use it if you have a specific need for it (which should essentially be limited to working with Kobo's nickel, or Kobo's kernels).

The pocketbook TC aims for maximum backward compatibility while still keeping inkview support.

The remarkable TC aims for FW >= 2.x compatibility.

The bookeen TC has only been tested on AWA13 devices, but should theoretically handle OMAP3611 ones, too.

Only actively tested on Linux hosts.
May work on macOS with some efforts, if you follow crosstool-ng's recommendations on the subject. This is only bound to get worse.
May work on Windows with even more efforts, but I wouldn't bother.
When in doubt, use a Debian VM.