k8jam is using pkg-config to detect libraries. SDL2 mixer might have a different name. i am testing for "SDL2_mixer", but it might be "SDL2_Mixer"… or might have no .pc file at all. also, there might be a conflict between 32-bit and 64-bit libraries — pkg-config is using 64-bit libs, and it just happened to work. i never really tried to build k8I on 64-bit system, so i simply don't know.
fejoa wrote
Very pleasant playing experience vasiliy, and great ergonomic improvements, thanks heaps!
thank you!
i believe that color printer could be easily integrated in vanilla. it is using two control codes: "\1N" and "\2". the former sets the color from some predefined set (or you can use "\1#nnn|" for hex RGB (3 or 6 chars), the latter resets everything back to the "default" color. and it is easy to use `RawTextData` object to reimplement `SplitString()`. also, `str.GetSize()` should be replaced with `str.Length()` in several places — `Length()` calculates string length without control codes (also using `RawTextData` iterator).
once all text printing methods understand colors, colors could be used anywhere, and it is possible to gradually introduce color coding. or even imlement it as option — printing routines will simply ignore control codes according to the flag.
this is prolly the easiest thing to port.
p.s.: `RawTextData` is useful, because it tracks the current color, so word wrapping routine can use it to start the new line with the correct color. see `WrapDataFont` object (silly name, i know

, which implements word wrapping with color code propagation. it uses `CharWidth()` method to get char width, which can simply always return `8` to implement monospace wrapping.
p.p.s.: `k8jam -jN` works too, just like you expect it to work with `make`.