View Single Post
Old 10-19-2010, 05:52 PM   #12
LoneTech
Zealot
LoneTech knows the square root of minus one.LoneTech knows the square root of minus one.LoneTech knows the square root of minus one.LoneTech knows the square root of minus one.LoneTech knows the square root of minus one.LoneTech knows the square root of minus one.LoneTech knows the square root of minus one.LoneTech knows the square root of minus one.LoneTech knows the square root of minus one.LoneTech knows the square root of minus one.LoneTech knows the square root of minus one.
 
Posts: 135
Karma: 7767
Join Date: Oct 2010
Device: PocketBook Pro 903
Smile

The more I read, the more I like PocketBook service. I was intimidated at first by finding only cyrillic conversation at the pocketbook-free project, but at this point, I have ordered a 903 and gotten the inkView demo in the SDK to run. I would like to participate in documenting development for the PocketBooks in English.

For my first little tip: The SDK apps look for some resources, such as fonts, in a bunch of places - /ebrmain and /mnt/ext1 among them. Symlinking the ebrmain directory included in the SDK to /ebrmain did the trick. This is probably mentioned in the readme, but I couldn't read it.

Next would be figuring out how to compile a program. Perhaps this sort of thing could be collected on the mobileread wiki? Considering the devhub, it looks on topic.

By the way, it feels clumsy dealing with winelib. I understand inkview was written with win32 APIs for emulation, but it would be easier for us GNU/Linux developers with a more native approach, such as SDL. My initial attempt at building grays hit a winegcc not found.

Second add: Another step complete! After installing ia32-libs-dev, libc6-dev-i386, libwine-dev, and lib32z1-dev, grays compiled with a simple make. Unlike the precompiled inkdemo, the freshly built program expected the whole SDK in /usr/local/pocketbook. Looking good!

Third add: Finding keynames-nanox.xml suggests that inkView may use the win32-like MicroWindows API. In that case using winelib represents much less effort than using SDL, and it wasn't that hard to install libwine-dev, so don't bother changing that part.

Last edited by LoneTech; 10-19-2010 at 06:21 PM.
LoneTech is offline   Reply With Quote