xmahjongg for Kindle as Kual extension - Page 5

sguerrini97 · 08-17-2016, 07:22 AM

The original author suggested me to use gifsicle to resize the GIFs: https://www.lcdf.org/gifsicle/
I tried it and the GIFs are working fine. However I still don't like the result, the best we can do is probably redraw them from scratch at a proper resolution.

@wodan16 yep it did a great jump lol, no problem

Hanspeter · 08-26-2016, 04:12 PM

So here is Version 0.6 but the tile set is changed to "thick" or "thick_k3" as you can see here better with stone is on top of the other stones.

HaPe

nasser · 08-28-2016, 03:46 AM

Layout "schoon" doesn't work.
Typo in "menu.json" file.

Code:

"action": "bin/start_schoon.sh",

should be changed to

Code:

"action": "bin/start.sh",

Hanspeter · 08-28-2016, 06:14 AM

Quote:

Originally Posted by nasser

Layout "schoon" doesn't work.
Typo in "menu.json" file.

Code:

"action": "bin/start_schoon.sh",

should be changed to

Code:

"action": "bin/start.sh",

Thank, fixed.

zxczxc · 09-19-2016, 05:14 PM

Quote:

Originally Posted by sguerrini97

If you are still looking in how to setup a cross toolchain, it's very simple on debian (should work on Ubuntu too):

Spoiler:

I think what knc1 suggested is a better approach, just wanted to show an easier way.

Edit:
Here is what knc1 suggested https://wiki.debian.org/QemuUserEmulation
Get the xmahjong source then

Code:

./configure --build=x86_64-linux-gnu --host=arm-linux-gnueabi
make

Binary file is "src/xmahjongg"
When I run it I get the same result as the first screenshot OP posted

Would you mind explaining quickly the comparison of/positives and negatives of:
1. installing the cross compiler toolchain,
2. using qemu and compiling it on the (emulated) device.

You say you think knc1's idea of using qemu is better, why I don't understand why.
I want to build some code for kindle, but I'm not sure which method to follow.

I really appreciate it, thank you!

knc1 · 09-19-2016, 05:32 PM

Quote:

Originally Posted by zxczxc

- - - -
You say you think knc1's idea of using qemu is better, why I don't understand why.
I want to build some code for kindle, but I'm not sure which method to follow.

I really appreciate it, thank you!

Partly it is subjective, partly technical.

There is code and then there is code.
Many software projects include test routines.
Running under an emulated environment lets you do the "make test" or "make check" that is supplied with the code.

You can't do that in a cross-compile environment.

Combining the techniques of qemu-static and a chroot - -
Then you can native build, including the install steps, (using "DESTDIR" argument) without fear of over-writing your host's version of the files.

If your dead set on using a cross-compile build environment - -
Use Buildroot(.org) - if they don't already have in the build tree what you want - you can easily add it.
The Buildroot build environment is high-quality, used by commercial embedded development (and developers).

Of course, you can do both -
Have Buildroot turn out a tar-ball of your stuff and everything else that it is dependent on.
Then populate a qemu-static, chroot with that tar-ball and test the hell out of (without risking your Kindle (yet) ).

zxczxc · 09-20-2016, 11:34 AM

Quote:

Originally Posted by knc1

Partly it is subjective, partly technical.

Thanks, it's a learning experience.
I feel this stuff is so vast for people who are new!
I might even play with both methods, to get a feel for them, thanks for the information.

knc1 · 09-20-2016, 12:01 PM

Embedded programming is a post degree subject.
You should be able to pick it up on your own in just a few decades.

zxczxc · 09-21-2016, 08:54 AM

Quote:

Originally Posted by sguerrini97

If you are still looking in how to setup a cross toolchain, it's very simple on debian (should work on Ubuntu too): https://wiki.debian.org/CrossToolchains#Installation
Just use "armel" instead of "armhf" to have a working CC for Kindle.
Look at my Makefile here, you may need to change the one in the project (e.g. use arm-linux-gnueabi-gcc instead of gcc): https://github.com/sguerrini97/gtk_s...aster/Makefile
Header files are the same across platforms afaik, but you need the libraries either from the Kindle or from the debian armel packages.

I feel very stuck, I installed the crosstool chain, that part works, I have compiled a 'hello world' program, that compiles and runs on my kindle fine.
(After I understand how this way works, I want to try the qemu set up later on)

But when I try to compile code that requires X11 and needs '-lXtst -lX11', I get errors.

Code:

/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/bin/ld: cannot find -lXtst

Ok, so I copied the /lib/ and /usr/lib folders from the kindle,
I put them all in a folder called 'kindlelibs' in my ~/Documents, and include that folder to be searched in the makefile.

Code:

-L/home/user/Documents/kindlelibs

But NOW I get the error

Code:

/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/bin/ld: cannot find /lib/libpthread.so.0

That file exists in the same place -lXtst (lixXtst.so) is, and that was found, so why not libpthread.0.so?

I don't know why it is looking in /lib for that library, because I told it to look in my kindlelibs folder in my documents. I thought when looking for libraries/header files, the compiler/linker will search all directories you provide, no?

It's not sure if this is a simple problem to fix, sorry for the trouble.
Thanks

knc1 · 09-21-2016, 10:15 AM

Try first for more information, use the gcc option(s) to print out the search path being used for each item searched for.
Once we know how it is going wrong, it will be easier to fix.

The man(ual) command is your friend and recognized by web-search applications if you don't happen to have the documentation installed on your system.
man gcc
that should do the job for you.

zxczxc · 09-21-2016, 02:24 PM

Ok I added -print-search-dirs (that seems what I should be doing) - this is the output when I make:

Code:

make kindle
arm-linux-gnueabi-gcc -print-search-dirs -DBUILD_KINDLE myturn.c -o myturn -pthread -Wl,-rpath,../lib -L/usr/arm-linux-gnueabi/lib -L../lib -L/usr/X11/lib -L/home/user/Documents/kindlelibs -L/home/user/Documents/kindlelibs/lib -lXtst -lX11
install: /usr/lib/gcc/arm-linux-gnueabi/4.9/
programs: =/usr/lib/gcc/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/:/usr/lib/gcc/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/bin/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/bin/arm-linux-gnueabi/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/bin/
libraries: =/usr/lib/gcc/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/lib/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/lib/arm-linux-gnueabi/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/lib/:/lib/arm-linux-gnueabi/4.9/:/lib/arm-linux-gnueabi/:/lib/:/usr/lib/arm-linux-gnueabi/4.9/:/usr/lib/arm-linux-gnueabi/:/usr/lib/

So it seems the problem is the kindlelibs dir (bolded in red) that I thought I added, doesn't show up in the libraries that gcc is searching.

Did I add it wrong? (It did something because it seems to provide the libXtst.so, without it I got this error)

knc1 · 09-21-2016, 02:37 PM

Hmm...
Hard to tell from that, all I can suggest (since I can't read your makefile from here):

Finding and fixing the cause of the visible errors might expose the problem.
First glaring problem:

Code:

:/usr/lib/

Will search the host libraries, which will not be ARM code, if it was, you wouldn't be cross-compiling.

See if you can find where that is getting added to the path.
Other errors might be near-by.

At worse - you have a make file not written with cross-compiling in mind.
(Did I mention? Cross-compiling can be a real bitch. That is why people use build systems for that purpose.)

zxczxc · 09-21-2016, 03:08 PM

Quote:

Originally Posted by knc1

Hmm...
Hard to tell from that, all I can suggest (since I can't read your makefile from here):

Finding and fixing the cause of the visible errors might expose the problem.
First glaring problem:

Code:

:/usr/lib/

Will search the host libraries, which will not be ARM code, if it was, you wouldn't be cross-compiling.

See if you can find where that is getting added to the path.
Other errors might be near-by.

At worse - you have a make file not written with cross-compiling in mind.
(Did I mention? Cross-compiling can be a real bitch. That is why people use build systems for that purpose.)

Ok so here is the makefile:

Code:

CROSS_COMPILE = arm-linux-gnueabi-
CFLAGS = -pthread
LDFLAGS = -Wl,-rpath, -L/usr/arm-linux-gnueabi/lib  -L/home/user/Documents/kindlelibs -L/home/user/Documents/kindlelibs/lib -lXtst -lX11
SRC = myturn.c
OUT = myturn

# -print-search-dirs

kindle: $(SRC)
	$(CROSS_COMPILE)gcc -DBUILD_KINDLE $(SRC) -o $(OUT) $(CFLAGS) $(LDFLAGS)

clean:
	rm $(OUT)

I have done some projects for Playstation Vita, Nintendo 3DS, cross compiling for them seemed easy compared to this! Although I admit it is a bit more documented/spoonfed!

Code:

make kindle
arm-linux-gnueabi-gcc -print-search-dirs -DBUILD_KINDLE myturn.c -o myturn -pthread -Wl,-rpath, -L/usr/arm-linux-gnueabi/lib  -L/home/user/Documents/kindlelibs -L/home/user/Documents/kindlelibs/lib -lXtst -lX11
install: /usr/lib/gcc/arm-linux-gnueabi/4.9/
programs: =/usr/lib/gcc/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/:/usr/lib/gcc/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/bin/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/bin/arm-linux-gnueabi/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/bin/
libraries: =/usr/lib/gcc/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/lib/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/lib/arm-linux-gnueabi/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/lib/:/lib/arm-linux-gnueabi/4.9/:/lib/arm-linux-gnueabi/:/lib/:/usr/lib/arm-linux-gnueabi/4.9/:/usr/lib/arm-linux-gnueabi/:/usr/lib/

Right at the end there, I see /usr/lib/ which you said is not good... but I am never providing that path...
What about my PATH environment variable, that must be a consideration too...?

Code:

echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

I don't see /usr/lib - so I assume not.

Thanks for all this help

lucida · 09-21-2016, 03:30 PM

Quote:

Originally Posted by zxczxc

Ok so here is the makefile:

Code:

CROSS_COMPILE = arm-linux-gnueabi-
CFLAGS = -pthread
LDFLAGS = -Wl,-rpath, -L/usr/arm-linux-gnueabi/lib  -L/home/user/Documents/kindlelibs -L/home/user/Documents/kindlelibs/lib -lXtst -lX11
SRC = myturn.c
OUT = myturn

# -print-search-dirs

kindle: $(SRC)
	$(CROSS_COMPILE)gcc -DBUILD_KINDLE $(SRC) -o $(OUT) $(CFLAGS) $(LDFLAGS)

clean:
	rm $(OUT)

I have done some projects for Playstation Vita, Nintendo 3DS, cross compiling for them seemed easy compared to this! Although I admit it is a bit more documented/spoonfed!

Code:

make kindle
arm-linux-gnueabi-gcc -print-search-dirs -DBUILD_KINDLE myturn.c -o myturn -pthread -Wl,-rpath, -L/usr/arm-linux-gnueabi/lib  -L/home/user/Documents/kindlelibs -L/home/user/Documents/kindlelibs/lib -lXtst -lX11
install: /usr/lib/gcc/arm-linux-gnueabi/4.9/
programs: =/usr/lib/gcc/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/:/usr/lib/gcc/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/bin/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/bin/arm-linux-gnueabi/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/bin/
libraries: =/usr/lib/gcc/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/lib/arm-linux-gnueabi/4.9/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/lib/arm-linux-gnueabi/:/usr/lib/gcc/arm-linux-gnueabi/4.9/../../../../arm-linux-gnueabi/lib/:/lib/arm-linux-gnueabi/4.9/:/lib/arm-linux-gnueabi/:/lib/:/usr/lib/arm-linux-gnueabi/4.9/:/usr/lib/arm-linux-gnueabi/:/usr/lib/

Right at the end there, I see /usr/lib/ which you said is not good... but I am never providing that path...
What about my PATH environment variable, that must be a consideration too...?

Code:

echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

I don't see /usr/lib - so I assume not.

Thanks for all this help

I use amazon's own toolchain and here is a quick instruction:

https://www.mobileread.com/forums/sho...1&postcount=34

zxczxc · 09-21-2016, 03:44 PM

Quote:

Originally Posted by lucida

I use amazon's own toolchain and here is a quick instruction:
https://www.mobileread.com/forums/sho...1&postcount=34

Ok so I will download this and inside there will be a toolchain to compile - sounds good!
https://kindle.s3.amazonaws.com/Kind...4910023.tar.gz

The instructions seem simple. When I copy the kindle libs from kindle to the host, I copy /lib/ or /usr/lib - or both (or is there more I missed?)

Thanks for all the help.

-- I assumed Amazon's toolchain was in the source code... I don't see it.
Embarrassing, it must be somewhere on Amazon's site, I'll keep looking.

- found it, it was there after all - (build_linaro-gcc_4.8.3.tar.gz)
I'm building it now

08-28-2016, 03:46 AM	#63
nasser Evangelist Posts: 475 Karma: 445678 Join Date: Feb 2010 Device: Too many..	Layout "schoon" doesn't work. Typo in "menu.json" file. Code: "action": "bin/start_schoon.sh", should be changed to Code: "action": "bin/start.sh",

09-21-2016, 02:37 PM	#72
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Hmm... Hard to tell from that, all I can suggest (since I can't read your makefile from here): Finding and fixing the cause of the visible errors might expose the problem. First glaring problem: Code: :/usr/lib/ Will search the host libraries, which will not be ARM code, if it was, you wouldn't be cross-compiling. See if you can find where that is getting added to the path. Other errors might be near-by. At worse - you have a make file not written with cross-compiling in mind. (Did I mention? Cross-compiling can be a real bitch. That is why people use build systems for that purpose.)

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
CPU Governor Menu (KUAL extension)	knc1	Kindle Developer's Corner	41	09-16-2021 03:54 PM
kual extension to open a book	shoelesshunter	Kindle Developer's Corner	14	08-16-2016 01:30 PM
Is there a Kual Extension/add-on for cloud	eduardomb	Kindle Developer's Corner	19	07-08-2016 06:43 PM
is there any KUAL extension development guide?	fangzi	Kindle Developer's Corner	2	01-02-2014 11:11 AM

08-17-2016, 07:22 AM	#61
sguerrini97 Enthusiast Posts: 27 Karma: 12 Join Date: Jan 2016 Device: KT2	The original author suggested me to use gifsicle to resize the GIFs: https://www.lcdf.org/gifsicle/ I tried it and the GIFs are working fine. However I still don't like the result, the best we can do is probably redraw them from scratch at a proper resolution. @wodan16 yep it did a great jump lol, no problem

09-20-2016, 12:01 PM	#68
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Embedded programming is a post degree subject. You should be able to pick it up on your own in just a few decades.

09-21-2016, 10:15 AM	#70
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Try first for more information, use the gcc option(s) to print out the search path being used for each item searched for. Once we know how it is going wrong, it will be easier to fix. The man(ual) command is your friend and recognized by web-search applications if you don't happen to have the documentation installed on your system. man gcc that should do the job for you.

Advert

Advert