I'm using scratchbox 2, the maemo development cross-compilation environment. When compiling code for the ARM target, I think scratchbox 2 is using the native ARM gcc compiler, which runs very slow on my x86 machine. I think it should be using an ARM cross-compiler, compiled for x86, that runs much faster. Sorry for the lack of details ...
I'm trying to follow section 3.4.2, starting on page 31 of this manual. However, as I have configured my target to be DIABLO_ARMEL rather than DIABLO_X86, I have gotten different results for this command: [sbox-DIABLO_X86: ~] > gcc -Wall -g gtk_helloworld-1.c \ ‘pkg-config --cflags gtk+-2.0‘ -o gtk_helloworld-1 \ ‘pkg-config --libs gt...
Hello, I've been using sbox with a Make-based codebase with no problems. Now I'm using a scons-based codebase, and am getting some odd problems. It seems that within scratchbox, scons can't find g++. For example, it attempts to execute things like: o hello hello.c When it should be doing: g++ -o hello hello.c So presumably its g++ s...
When I compile my Qt Maemo application in Scratchbox 1, all of the image resources appear completely messed up and corrupted, and the program runs extremely slow. This only happens for the armel target, and works fine in i386. I also get these errors at the console: X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major op...
I am building a sharing-service for maemo5. In the example plugin they are calling ULOG_INFO_L at a lot of places, so I have adopted this for my service as well. The problem is that I can't find where the messages goes. Reading osso-log.h I should define DEBUG or OSSOLOGCOMPILE, which I do and OSSOLOG_STDOUT or OSSOLOG_SYSLOG. I have tr...