Quote:
Originally Posted by guyanonymous
While it's nice for the SDKs to become available, wouldn't it be nice if Pocketbook got their act together with proper file naming that indicated device/version etc. Every time something new is released by pocketbook there seems to be confusion about the device its for, and the real version; even a simple change log would be a bonus!
|
The SDK pointed to by Tulapi has headers, libraries and tools for both the old arm-linux (302, 360) and newer arm-none-linux-gnueabi (pro, 360+) architectures, so it looks like it's supposed to be used by everyone. I tried looking at the differences between the new inkview.h header file and the one last distributed by sergeyvl12 to see what changed in the library, but it's hard to say because they cleaned up their programming style and changed all of the constant "char*" function parameters to "const char*", so their are a lot of differences. So, yes, a ChangeLog would be nice, even though it would likely be in Ukrainian.
I'm going to try copying the new header and library into sergeyvl12's last SDK later today and give it a quick test.
Edit: I copied over the new inkview.h and libinkview.so files into the appropriate places in sergeyvl12's pocketbook_arm_gnueabi directory, and the build of a test app went fine (after I also copied over libpng12.so from the new SDK to the /usr/arm-linux-gnueabi/lib directory). The new app seemed to work on my 902 with 2.0.4 firmware. So I guess that answers my question to mtravellerh above about whether the new SDK is compatible with older firmware releases.