View Single Post
Old 07-14-2011, 05:58 PM   #20
rkomar
Wizard
rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.
 
Posts: 3,058
Karma: 18821071
Join Date: Oct 2010
Location: Sudbury, ON, Canada
Device: PRS-505, PB 902, PRS-T1, PB 623, PB 840, PB 633
I downloaded both (i386 and amd64) versions, and the only difference is that libinkview.so has been moved from /usr/lib/ to /lib32/ in the amd64 version. Everything else is the same. I was previously running sergeyvl12's older SDK under a 32-bit system inside VirtualBox. I don't mind using the VirtualBox emulator for the BUILD=emu stuff, since I don't do it that often. But I was hoping to be able to build the BUILD=arm and BUILD=arm_gnueabi targets natively on my 64-bit system. Oh well.

If you can cross-compile to the ARM targets now, then you already have the 32-bit compatibility libraries installed on your system. The /usr/bin/arm-* programs would not run without them on a 64-bit system.

If you are installing using a package manager, then 'ldconfig' is probably already being executed on your system. Running /sbin/ldconfig -p | grep inkview will show you if libinkview.so is already cached and can be used for building. If it isn't, then just run 'ldconfig' as root, and it will be.

I don't know how to set up QtCreator or any other IDE. I'm a command-line kind of guy .
rkomar is offline   Reply With Quote