Welcome to the Official BlackBerry Support Community Forums. This is your resource to discuss support topics with your peers, and learn from each other. New to the forum? Please visit the ‘Getting Started’ link below.
How do I actually go about printing to the console from one of my cpp files? All I'm trying to do is print some data so I can see what I'm working with and then move forward accordingly.
When working on Android apps in Eclipse, all I had to do was type System.out.println(); and fill it with any object or variable and it would spit it out. I can't seem to find anything similar here.
qDebug() and similar forms of output should go to the "slog2" output for the app, which writes a special file into a RAM drive area where it can be monitored from Momentics using some View Log feature (you'll have to google or search the forum... I don't use it) or by connecting to the device with SSH and using "slog2info -w" or a similar form of that command.
Any output that doesn't get redirected there should end up in the logs/log output file, which is written to the actual flash filesystem and therefore a less desirable target than slog2, and you can also view that either through the IDE or via SSH, in this case just by using "cat" or possibly "tail -f logs/log" after changing the current directory to your app's sandbox folder.
Note that qDebug() should already be "enabled" by default now, but with the output going to the slog2 output as I mentioned. What you've found is a way to redirect it to the old logs/log output, in the actual flash filesystem. That works, but has disadvantages as noted earlier.
(Just noting that for others who will read this later.)
The qDebug() function provides additional functionality that fprintf() doesn't provide, useful in C++ programs. There are many ways to get output though... if fprintf() works for you, by all means use it. I'd strongly suggest in a release version that you #ifdef those out, however, so that your app is not constantly writing to flash memory whenever it runs. That's why switching to slog2(), even in a C app, would be worth considering.
