linking to gtk

[chris_c]

I've successfully compiled xlib applications and even source using Xaw by copying kindle libs to my pc and using arm-linux-gnueabi-gcc-4.6

However programming with Athena widgets is as much fun as stabbing yourself in the eye with a rusty fork...

I tried out compiling simple gtk source code, but it seems to want to link pthreads from a absolute path :/

anyone got gtk apps compiled for the kindle ? (ideally without a chroot jail ?)

[knc1]

Originally Posted by chris_c

I've successfully compiled xlib applications and even source using Xaw by copying kindle libs to my pc and using arm-linux-gnueabi-gcc-4.6

However programming with Athena widgets is as much fun as stabbing yourself in the eye with a rusty fork...

I tried out compiling simple gtk source code, but it seems to want to link pthreads from a absolute path :/

anyone got gtk apps compiled for the kindle ? (ideally without a chroot jail ?)

What absolute path?
gcc -v .... will help you answer that question.
Include in your reply the full gcc command line being used.

What Kindle?
Yes, it makes a difference to the answer.

P.S: What version of gtk or gtk2?

[chris_c]

never mind, I tried again from scratch and typically can't replicate the problem, on the plus side it does mean I can compile gtk+-2.0 apps for my kindle touch.

-- the quick and dirty (not recommended) cross compile bodge --

to avoid having a bunch sym links when copying the kindle libs to my pc I dropped the version numbers after the .so

so

libBlah-2.0.so.1.2.3

becomes

libBlah-2.0.so

I stuck these in a local (to my dev folder) directory called libs

I'm using the includes from the host (which seems to work!)


arm-linux-gnueabi-gcc-4.6 gtk.c `pkg-config --cflags gtk+-2.0` -L./libs -lgtk-x11-2.0 -lgdk-x11-2.0 -lXrender -lXinerama -lXext -latk-1.0 -lcairo -lexpat -lffi -lfontconfig -lfreetype -lgdk_pixbuf-2.0 -lgio-2.0 -lglib-2.0 -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lpango-1.0 -lpangocairo-1.0 -lpangoft2-1.0 -lpixman-1 -lpng12 -lxcb-render -lxcb-shm -lXdamage -lXfixes -lz -lX11 -lxcb -lXau -lXdmcp -o gtktest

needless to say I'll be making a Makefile before long....

[knc1]

Destroying the soname, naming conventions is not something to be recommended.
Are you doing this work on a file system that does not support symbolic links?

Using the host includes is not something to be recommended.
That will fail as soon as you encounter an include that contains code or one of the systems (host or target) changes so that the includes are not compatable.

I would strongly suggest that you spend your time setting up a proper cross-compile environment before wasting your time with creating a Makefile built to fail.

[chris_c]

Originally Posted by chris_c

-- the quick and dirty (not recommended) cross compile bodge --

it works just fine, sufficient that I have almost finished a quick sudoku app

bare in mind the includes that user code includes are platform agnostic...

[knc1]

Originally Posted by chris_c

it works just fine, sufficient that I have almost finished a quick sudoku app

bare in mind the includes that user code includes are platform agnostic...

Keep in mind that is the way it is **supposed** to be.
Which unfortunately is not guaranteed in the real world.

[chris_c]

if by supposed you mean the whole point of a cross platform GUI library, then, yes )

[knc1]

Originally Posted by chris_c

if by supposed you mean the whole point of a cross platform GUI library, then, yes )

I wasn't very clear was I? My bad. I meant as a general rule, inclusive of GUI libraries.

But we are on the same track here.

For the non-programmers reading this -
"Includes" in the "C" (or "C++") language are "header files" and the design intent behind header files is that they should never cause (or contain) code generation statements.

Not all source code authors follow that rule.

Here, this "quick and dirty" happens to work, today.
It may not work tomorrow and the O.P. is aware of this, this post is just so that other readers are aware also.