Forum Replies Created
-
Posts
-
Hi,
For embedded projects VisualGDB always uses the GDB that comes with your toolchain. The easiest way to override it would be by copying the toolchain to a different directory and adding a GDBExecutable element to toolchain.xml:
<Toolchain ...> <GDBExecutable>other-gdb.exe</GDBExecutable>
Hi,
We are currently planning to release the first beta around the end of November – beginning of December.
You can include resources like image files by modifying the Makefile. See this tutorial for an example of including a .png file.
Hi,
It’s hard to answer that question from just looking at the project source page. What hardware is the project targeting? What toolchain is it using?
Hi,
Good to know the workaround works. It’s surprising that the cc1plus requires more than 2 gigabytes of RAM, how large is your source file and the included headers (you can find it out by preprocessing it to a file using -E instead of -c)?
Hi,
Please try viewing the Android log (run adb.exe logcat) or launch debugging with VisualGDB and check for errors in the GDB Session/logcat windows.
Hi,
The problem with Eclipse is that every version stores the settings a little bit differently, so there is no consistent way of importing them automatically.
We have received a lot of feedback recently about debugging embedded projects built elsewhere and will be extending our Quick Debug feature with Embedded Quick Debug in the next version. Until then the suggested workaround is to import your projects.
Hi,
You can try following our tutorial on importing projects from CooCox IDE: http://visualgdb.com/tutorials/arm/coocox/
Let us know if that works.
Hi,
What exactly do you mean by “crashed”? Do you get some specific message? Can you attach a screenshot? Does it also crash when you run the debug APK without debugging?
Hi,
Thanks for your feedback. We have extensively tested our IntelliSense engine with the auto variables, nested classes and template classes and could not reproduce the problems you are reporting. Furthermore, many of our users reported that they are successfully using the Clang IntelliSense engine with complex C++11 code. Hence it looks like the problem on your side is caused by some configuration issue (e.g. incompatible CFLAGS, missing include directory, or some very specific statement that breaks IntelliSense). We will be happy to help you solve it, but we would need more information on reproducing it.
Could you reproduce it on a stand-alone project and send it to us? If not, could you send us a screenshot of the problem along with the CFLAGS/CXXFLAGS from the project view in the Clang IntelliSense Diagnostics console?
Hi,
We have provided a solution in this post.
Hi,
It looks like the Espressif guys forgot to declare this function in their SDK. Please feel free to add the following declaration to espmissingincludes.h and include the file from your projects:
int os_printf_plus(const char *format, ...) __attribute__ ((format (printf, 1, 2)));
Hi,
No problem. We have updated our Beaglebone tutorials to clearly state the Angstrom is deprecated and also published a new tutorial showing how to create an app for Beaglebone.
If you encounter further problems or find outdated information in our documentation, feel free to let us know so that we could update the documentation or provide fixes/workarounds.
Hi,
Perhaps some libraries are missing in the sysroot. Please try our latest Beaglebone toolchain. It also contains the pre-built Qt binaries, so you can simply deploy them to your Beaglebone and start using Qt.
We have also published the final version of the tutorial: http://visualgdb.com/tutorials/beaglebone/qt5/cross-compile/
You should be able to create an app for it by following the Raspberry tutorial without cross-compiling the entire Qt framework (note that Qmake in the toolchain has the c:\SysGCC\Beaglebone directory hardcoded; our next tutorial will show how to adjust it, but for now please place the Beaglebone toolchain to c:\SysGCC\Beaglebone).
