borzunov / remoteink Goto Github PK

How to manage the "build=emu" on compiling the executable (of remoteinkd) for emulation of a pocketbook application under linux.

Sound easy but you might encounter problems. That is to say the BUILD=gnueabi works fine, but when it is time to compile the application with BUILD=emu for emulation and test it on linux desktop, lots of problems occur.

1. Doesn't find the libinkview.so, problems of freetype/freetype.h, ft2build.h, etc.
   exemple : inkview.h:25:22: fatal error: ft2build.h: Aucun fichier ou dossier de ce type

2. in the linkers'pass, it just doesn't have the dependancies with other libraries or can't find them..

3. Once he application is compiled fine : when it is time to run it, it just doesn't find the shared libray libinkview.so .

The idea is to start from scratch with the SDK downloadable from github for pocketbook (link).
Assuming you have placed the SDK in the drawer : $HOME/project

ls $HOME/project may give you more or less something like :
development ldconfig.txt readme.txt sources
FRSCSDK ldconf.txt PBSDK releases system

PBSDK/lib contains the important shared library : libinkview.so .

For compiling, you will need to know where to find the freetype on your computer.
Use : freetype-config --cflags
on my config i get : -I/usr/include/freetype2
for linker's pass :
Use : freetype-config --libs
on my config i get : -L/usr/lib/i386-linux-gnu -lfreetype -lz -lpng12

if you don't have freetype-config installed, just do : sudo apt-get install freetype-config

for the compiler to locate inkview.h  : -I$(SDKDIR)/FRSCSDK/include/

Therefore the file common.mk has to be updated with the following changes : ---------------------

Make sure SDKDIR points to the right drawer SDKDIR=…/project

ifeq ($(BUILD), emu)
PROJECT = $(OBJDIR)/$(OUT)
LIBS += -linkview
INCLUDES += -I$(SDKDIR)/FRSCSDK/include/ `freetype-config --cflags`
CC = gcc
CFLAGS += -O0 -D__EMU__ -DIVSAPP -g -m32
CXX = g++
CXXFLAGS += -O0 -D__EMU__ -DIVSAPP -g -m32
LD = g++
LDFLAGS += -m32
endif

When compiled correctly, launch the executable file found in ./obj_emu
If it doesn't find the shared library libinkview.so then you will need to copy libinkview.so to a directory where the program is looking for it.
To know where, just type in a terminal :

export LD_DEBUG=libs

Then launch the program in the terminal. You will see all the locations where it is searching for the library. Just find one place and copy libinkview.so from PBSDK to this new location.

One of the locations where you can copy libinkview.so is :
/usr/lib

(export LD_DEBUG = ) to remove the option.

Your emulation of the application for pocketbook should launch correctly now.

I followed the steps from the installation guide:

$> make
mkdir obj
gcc -c -std=gnu99 -pedantic -Wall -Wshadow -O3 -o obj/exceptions.c.o -MTobj/exceptions.c.o -MFobj/exceptions.c.d -MMD -MP ../common/exceptions.c
gcc -c -std=gnu99 -pedantic -Wall -Wshadow -O3 -o obj/ini_parser.c.o -MTobj/ini_parser.c.o -MFobj/ini_parser.c.d -MMD -MP ../common/ini_parser.c
In file included from ../common/ini_parser.c:1:
../common/ini_parser.c: In function ‘ini_load’:
../common/ini_parser.c:10:33: warning: ‘%s’ directive output may be truncated writing up to 254 bytes into a region of size 239 [-Wformat-truncation=]
   10 | #define ERR_INI_UNKNOWN_SECTION "Unknown section \"%s\" in \"%s\""
      |                                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../common/exceptions.h:28:49: note: in definition of macro ‘PANIC_WITH_DEFER’
   28 |    snprintf(exc_message, EXC_MESSAGE_SIZE, __VA_ARGS__);\
      |                                            ^~~~~~~~~~~

../common/ini_parser.c:57:50: note: in expansion of macro ‘ERR_INI_UNKNOWN_SECTION’
   57 |                           PANIC_WITH_DEFER(ERR_INI_UNKNOWN_SECTION,
      |                                            ^~~~~~~~~~~~~~~~~~~~~~~

../common/ini_parser.c:10:52: note: format string is defined here
   10 | ERR_INI_UNKNOWN_SECTION "Unknown section \"%s\" in \"%s\""
      |                                            ^~

In file included from ../common/ini_parser.c:1:
../common/exceptions.h:28:9: note: ‘snprintf’ output 25 or more bytes (assuming 279) into a destination of size 256
   28 |         snprintf(exc_message, EXC_MESSAGE_SIZE, __VA_ARGS__);\
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../common/ini_parser.c:57:33: note: in expansion of macro ‘PANIC_WITH_DEFER’
   57 |                                 PANIC_WITH_DEFER(ERR_INI_UNKNOWN_SECTION,
      |                                 ^~~~~~~~~~~~~~~~
gcc -c -std=gnu99 -pedantic -Wall -Wshadow -O3 -o obj/utils.c.o -MTobj/utils.c.o -MFobj/utils.c.d -MMD -MP ../common/utils.c
gcc -c -std=gnu99 -pedantic -Wall -Wshadow -O3 -o obj/control.c.o -MTobj/control.c.o -MFobj/control.c.d -MMD -MP control.c
gcc -c -std=gnu99 -pedantic -Wall -Wshadow -O3 -o obj/main.c.o -MTobj/main.c.o -MFobj/main.c.d -MMD -MP main.c
gcc -c -std=gnu99 -pedantic -Wall -Wshadow -O3 -o obj/options.c.o -MTobj/options.c.o -MFobj/options.c.d -MMD -MP options.c
gcc -c -std=gnu99 -pedantic -Wall -Wshadow -O3 -o obj/profiler.c.o -MTobj/profiler.c.o -MFobj/profiler.c.d -MMD -MP profiler.c
gcc -c -std=gnu99 -pedantic -Wall -Wshadow -O3 -o obj/screen.c.o -MTobj/screen.c.o -MFobj/screen.c.d -MMD -MP screen.c
gcc -c -std=gnu99 -pedantic -Wall -Wshadow -O3 -o obj/security.c.o -MTobj/security.c.o -MFobj/security.c.d -MMD -MP security.c
gcc -c -std=gnu99 -pedantic -Wall -Wshadow -O3 -o obj/shortcuts.c.o -MTobj/shortcuts.c.o -MFobj/shortcuts.c.d -MMD -MP shortcuts.c
gcc -c -std=gnu99 -pedantic -Wall -Wshadow -O3 -o obj/transfer.c.o -MTobj/transfer.c.o -MFobj/transfer.c.d -MMD -MP transfer.c
mkdir bin
gcc -o bin/remoteinkd obj/exceptions.c.o obj/ini_parser.c.o obj/utils.c.o obj/control.c.o obj/main.c.o obj/options.c.o obj/profiler.c.o obj/screen.c.o obj/security.c.o obj/shortcuts.c.o obj/transfer.c.o  -lcrypt -lfontconfig -lImlib2 -lm -lpthread -lrt -lX11 -lxcb -lxcb-keysyms -lxcb-shm -lxcb-xfixes
/usr/bin/ld: obj/profiler.c.o:(.bss+0x0): multiple definition of `f'; obj/ini_parser.c.o:(.bss+0x200): first defined here
/usr/bin/ld: obj/screen.c.o:(.bss+0x28): multiple definition of `display'; obj/main.c.o:(.bss+0x228): first defined here
/usr/bin/ld: obj/security.c.o:(.bss+0x260): multiple definition of `f'; obj/ini_parser.c.o:(.bss+0x200): first defined here
/usr/bin/ld: obj/shortcuts.c.o:(.bss+0x20): multiple definition of `display'; obj/main.c.o:(.bss+0x228): first defined here
/usr/bin/ld: obj/shortcuts.c.o:(.bss+0x18): multiple definition of `screen'; obj/screen.c.o:(.bss+0x20): first defined here
/usr/bin/ld: obj/shortcuts.c.o:(.bss+0x10): multiple definition of `root'; obj/screen.c.o:(.bss+0x1c): first defined here
collect2: error: ld returned 1 exit status
make: *** [Makefile:18: bin/remoteinkd] Error 1

a) other e-readers like Kindle, Kobo, Onyx, Nook, Icarus?

b) the new Pocketbook models like the Inkpad?

Pocketbook Touch HD3, firmware version Dec '23
Raspberry pi 4B running normal Debian-based OS
Client app installed on PocketBook and configured to connection parameters

Symptom: when I connect the PocketBook the screen goes black - except twice it worked fine and gave me a perfect replica of the desktop, was able to zoom in, run wordgrinder in a window, etc. This morning, back to black. No command window open on the desktop so nothing black it could be zoomed in on.

When I Stop RemoteInk on the server the display on the PocketBook immediately reverts to normal.

Details: RemoteInk server starts, status running, and as I say I did get a successful display twice. The local hotspot on the Pi is working, the correct network parameters are configured on the client, and the connection starts. When it fails to connect (eg when I stopped the server or the wifi is off) I get a Connection Failed message on the PocketBook. So the issue is, I get a good connection, and the display is black.

Is this a known issue, and can anyone help me figure out how to get it working? As I said, it did display properly twice yesterday so I'm not sure what I'm doing or not doing wrong. Thanks!

Privet Aleksandr...

First of all - remoteink is wonderfull aplication. We have excellent use of it in sailplane cockpit as BeagleBoneBlack microcomputer screen - due to bright sunlight PaperInk is one of very few options with low power consumption... Transflective screens on phones or touchpads are extremely rare now...

We have mostly PocketBooks in the stores overhere (in Lithuania). Kindles and Kobos are only ordered online and should be illegaly rooted. Kindle Keyboard is our current screen, but we like PocketBook Touch, becuse using your application we do not need to be involved in hacking it...

RemoteInk is perfectly working on our Pocketbook Touch Lux2 (model 626) with 4.xx firmware, but it is obsolete now for several years. In 5.xx firmware client's screen is shifted down (I think it is somehow related to Status Bar - this is the size of shift down).

Please find some spare time and fix this for new PocketBook firmware. THANKS...

Respectfully,
Rolandas RAGAISIS
Kaunas, Lithuania...

P.S. You are welcome to visit us and fly our sailplanes in Lithuanian skies...

Hi, first let me congratulate you for this excellent program! I'm running archlinux and make sure to follow every step but it doesn't work. In journalctl the following message is displayed: Error on request to X server. I've tried different ports, firewall configuration, but with no success. The e-reader doesn't show anything and after two or three minutes gives the message: Failed to connect to 10.0.0."something":9312.

Could you please help me? Thanks a lot!

Hey! Is is possible to support color E-book, e.g. PocketBook 740 Color?

Hi, I have a question with my pocketbook, it is possible to use a keyboard to write in the book?

Hi, I wonder could X shared memory code be re-written so that socket transmission is used instead?

I'm trying to get remoteink working over SSH and it does not work with shm-* functions.
It works nicely if I run X11 on host itself, though.

UPD: looks like the problem is not with shared memory but with remoteinkd server itself. No additional error is thrown if shm* execs were disabled in code. Server running showing black screen on client.

This is really cool, it works and mirrors part of the desktop, I couldn't find this in the guide, is there a simple way to extend the desktop to the Pocketbook rather than mirror it? Or running a separate X-Server for it?

Hello Alexander and Nikolai,

I received a request to connect 2 devices together: Raspberry Pi 2 and Pocketbook Inkpad 3 as a screen via USB. Can't manage to get the USB connection via remoteink to work and ask you for any advice you could offer.

Wifi connection works without issues, but the person who made the request wants to avoid using wireless signals. Been trying to use a pl-25a1 USB2 chipset cable & USB2 (female) -> MicroUSB (male) for it. Inkpad 3 has been rooted and got USB networking turned on. When connected together via cable, Raspberry shows USB network IP and port, yet no interface pops up in remoteink, so I believe the issue could be on the Pocketbook side of things.

Do you know of compatibility between remoteink and Inkpad 3?
Do you know of any way to check if Inkpad 3 contains g_ether module?
Could the adapter be an issue in the USBNet connection?
Is the cable good for what I'm trying to do?

Hi, I have PocketBook Inkpad X. It's 10 inch screen device.
Can your client application work under Windows 10 OS ?
Thanks