Any thoughts here on how to fix this and actually get the debugger to.erm. Mac: Install MacPorts following these instructions: Once MacPorts is. So, two TOTALLY different OS's, a fresh install of Necessitas and fresh build of the app. 1: Package version for package atmel-qt-demo-init-dbg went backwards which would. Unexpected GDB stderr: "/opt/NecessitasQtSDK/android-ndk-r6b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gdb: /lib/libz.so.1: no version information available (required by /opt/NecessitasQtSDK/android-ndk-r6b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gdb) The ONLY hint I have at a problem is the console from whence I started Qt Creator says: (It's been sitting there for 15+ minutes now.) At this point, my phone sits there with a black screen (well, notification bar up top, but app area is black) and Qt Creator sits there at Setting Breakpoints. When using KDE and/or any other Qt desktop environment debug info may be. Debugmger starts, says thread created, starting inferior, loading symbols, and finally, Setting Breakpoints. By installing qtchooserAUR you can make the Qt binaries in /usr/bin (e.g. I updated ant, downloaded my project from google code, opened it in Necessitas, set buildmode to debug (arm 7a).annnndddd.still the EXACT same problem: In my fresh install of CentOS, I downloaded and installed necessitas-0.3-online-sdk-installer-linux. On Linux, this has to be done manually, the resulting binaries are too large because they contain all the debug information. This reduces the size of the binary files to be deployed. Alright, this is really starting to frustrate me - I downloaded and installed CentOS 6.3 - 32bit - in VirtualBox today on my Win 7 laptop. On Windows, debugging symbols are separated automatically from the binary files (.exe or.
0 kommentar(er)
