Testing pocketbook apps

sigizmund · 02-17-2020, 07:34 AM

Hey folks,

How do you test/debug your Pocketbook apps? The most straight forward way is, obviously, just cross-compile ARM code, install app on the device and run it - but edit/refresh cycle is long, debugging is cumbersome and %reasons% -- especially when building UI.

The approach which was suggested in the original SDK (pocketbook-free.sourceforge.net) was to use libinkview compiled for Windows, either by using Cygwin or compile on Linux using winegcc. On Linux I got as far as compiling the app, starting it with wine, and it crashes with access violation at some point; on Windows it even starts the app window and still crashes with access violation -- all of this before reaching my code (reasons for that is kinda hard to debug without having full source code).

Question is: how y'all do it? Ideally running app natively on your PC (Linux or Windows) would be ideal, but failing that, anything that allows to relatively easily run and debug app might help.

Thoughts?

ezdiy · 02-27-2020, 09:57 AM

The inkview windows sdk is rather aged and basically runs only on win xp. Luckily, fully working gdb is shipped with stock firmware. Best success I had was just cross compiling, deploy task (I'm using IDEA) configured to directly store the binary on the device, and then just launch it in gdb in there with debugging port the IDE then connects to. Then everything works as expected. You also need to do some symlinking so as to get include headers / source files correctly placed and recognized by gdb that runs on the reader.

sigizmund · 02-28-2020, 06:23 AM

Quote:

Originally Posted by ezdiy

The inkview windows sdk is rather aged and basically runs only on win xp. Luckily, fully working gdb is shipped with stock firmware. Best success I had was just cross compiling, deploy task (I'm using IDEA) configured to directly store the binary on the device, and then just launch it in gdb in there with debugging port the IDE then connects to. Then everything works as expected. You also need to do some symlinking so as to get include headers / source files correctly placed and recognized by gdb that runs on the reader.

That's really cool - do you think you can write a post describing how your setup works? Would be very interesting and useful for new generations of pocketbook hackers!

rkomar · 02-28-2020, 10:22 AM

There is some information on gdb in this thread: https://www.mobileread.com/forums/sh...d.php?t=222077. Since you already have gdb on your device, you can ignore the part about installing an external version with the libraries.

random42 · 03-10-2020, 10:11 AM

I thought people were doing most dev in qemu.

I'm also interested in how to get going, I wanted to see if I could get programs written in Rust working

02-17-2020, 07:34 AM	#1
sigizmund Member Posts: 24 Karma: 1088 Join Date: Dec 2009 Device: Pocketbook && Android	Testing pocketbook apps Hey folks, How do you test/debug your Pocketbook apps? The most straight forward way is, obviously, just cross-compile ARM code, install app on the device and run it - but edit/refresh cycle is long, debugging is cumbersome and %reasons% -- especially when building UI. The approach which was suggested in the original SDK (pocketbook-free.sourceforge.net) was to use libinkview compiled for Windows, either by using Cygwin or compile on Linux using winegcc. On Linux I got as far as compiling the app, starting it with wine, and it crashes with access violation at some point; on Windows it even starts the app window and still crashes with access violation -- all of this before reaching my code (reasons for that is kinda hard to debug without having full source code). Question is: how y'all do it? Ideally running app natively on your PC (Linux or Windows) would be ideal, but failing that, anything that allows to relatively easily run and debug app might help. Thoughts?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Pocketbook, Apps, and history	Nate the great	PocketBook	3	11-25-2014 11:15 AM
Replacement reading apps for Pocketbook	Nate the great	PocketBook	6	11-18-2014 07:54 PM
installing apps on pocketbook a10	willyloco	PocketBook	2	04-24-2012 03:05 AM
IQ Android Apps for PocketBook IQ 701	Dulin's Books	PocketBook	126	04-18-2012 07:01 PM
Android App for testing apps	nniesen	enTourage Archive	0	05-26-2011 02:40 AM

02-27-2020, 09:57 AM	#2
ezdiy Zealot Posts: 121 Karma: 156515 Join Date: Oct 2019 Device: KT, KPW4, PB740-2	The inkview windows sdk is rather aged and basically runs only on win xp. Luckily, fully working gdb is shipped with stock firmware. Best success I had was just cross compiling, deploy task (I'm using IDEA) configured to directly store the binary on the device, and then just launch it in gdb in there with debugging port the IDE then connects to. Then everything works as expected. You also need to do some symlinking so as to get include headers / source files correctly placed and recognized by gdb that runs on the reader.

02-28-2020, 10:22 AM	#4
rkomar Wizard Posts: 3,027 Karma: 18765431 Join Date: Oct 2010 Location: Sudbury, ON, Canada Device: PRS-505, PB 902, PRS-T1, PB 623, PB 840, PB 633	There is some information on gdb in this thread: https://www.mobileread.com/forums/sh...d.php?t=222077. Since you already have gdb on your device, you can ignore the part about installing an external version with the libraries.

03-10-2020, 10:11 AM	#5
random42 Junior Member Posts: 7 Karma: 10 Join Date: Jan 2020 Device: PB HD3 (632), Kindle Paperwhite	I thought people were doing most dev in qemu. I'm also interested in how to get going, I wanted to see if I could get programs written in Rust working

Advert

Advert