![]() ![]() With reference to your last comment though, I don't understand how people do serious application development on Android if the general consensus is that there's no debugging. He wasn't sure how programming worked anymore. I blew my little brother's mind (he's a CS student) by having this happen, then just deleting the errors, and then building the program just fine. ![]() To fix this, you actually need to go into the "Problems" list and delete the errors, or else it won't let you build the program correctly. However, as soon as you open up any C++ file in the editor, it immediately tries to do a bunc h of intelligent symbol linking and craps out, giving you a bunch of errors like juce::Rectangle is undefined or whatever. When you build in debug mode, the debugger will now at least be intelligent enough to tell you the symbolic name of the functions in the call stack, and so far it's seemed to be decent with watching data values. Right click on the project and go to Properties, then go to the C/C++ General category, then click "Paths and Symbols." In that, go to "Source Location," and then do "Link Folder." and create a link to the folder containing your source code. The second key is to add a link to your source code into the file itself. Note that last flag - that's needed for JUCE to go all the way into Debug mode. I did manage to get *something* working - the key is to make sure you set your build command to ndk-build NDK_DEBUG=1 CONFIG=Debug. Just in case you want to try the "ant debug" approach, i had a look in my magic spell book.Īdb -e install bin/projectname-debug.apk (for emulator)Īdb -d install bin/projectname-debug.apk (for device) Or could this be a DEBUG vs NDEBUG thing. That's eclipse for you! The environment where you can't "open" a project :-)īut seriously, what if you defined DEBUG manually somewhere to be sure. What is the full workflow that people are using and where does Eclipse fit into it? If I do ant debug and then try to Debug again in Eclipse, it rebuilds it as a non-debug build, which is insane. I've tried looking at a LOT of things, particularly right-clicking the build.xml file in Eclipse and doing "Ant Build." and tweaking the infinitude of settings present, but I can't seem to find the magic workflow. That's fine, but once I do that, then what? How do I run the program on the Android tablet, and then hook that into the debugger in Eclipse? How do I set up breakpoints and step through my code? The solution advanced on this forum is to go to the terminal and build using "ant debug" and "ant release" instead. It instead tries to set it up as a release build, so DBG() doesn't end up defined as anything. The basic issue is that if I try to do a "debug" build within Eclipse by going to Run -> Debug, it doesn't end up building it as a debug build. I'm so frustrated I want to headbutt my MacBook pro. I've spent a long time trying to figure out how to get debugging to work in Eclipse, so I can set up breakpoints and step through things. ![]()
0 Comments
Leave a Reply. |