Forum Replies Created
-
Posts
-
Hi,
Thanks for reporting this. This usually happens when the ‘working directory’ field was left empty and not related to changing the remote machine. We agree this is confusing and will add better handling for this in the next release.
Regarding the forum, it’s a known bug of the forum engine we are using. As a workaround, please paste the text to Notepad, then copy it to clipboard again and paste it on the forum. This should clear all extra formatting and work around this.
Hi,
Thanks, it looks indeed like your antivirus is interfering with the installation and deleting some files.
This is a known issue. Unfortunately modern antivirus software works by simply trying to locate known sequences inside exe files, so a large installer file with a compressed block of data will almost certain trigger a false positive. We submit those cases to antivirus vendors from time to time and get our files excluded, but it looks like this one is new.
Our best advice would be to disable your antivirus during installation.
Hi,
Please try looking at the GDB Session window when debugging. If you change the filter to show all gdb interaction, then you can scroll back to see how the commands you added to the startup commands got executed. You can also enter the “show remotetimeout” command in the field below the log during debugging and see its output immediately. You can also send the full gdb log for us to look at.
As for the steps you did, increasing the working space could have been the thing that helped with the error.
Hi,
Please note that the Custom build actions page in the VisualGDB Project Properties window is only available in the Custom and Ultimate editions of VisualGDB along with the rest of the custom features. This is can be why this page is not shown for you.
Hi,
Are you running the executable on the same raspberry pi 2 device or on another rasperry pi or Linux remote machine?
As the executable was built for a rasperry pi 2 device running raspian other Linux machines have different hardware and libraries and then the program cannot run there.
Hi,
You can add the “set remotetimeout” command on the GDB startup commands page in VisualGDB Project Properties.
Hi,
You can use the Custom post-build actions in VisualGDB Project Properties to copy files automatically after each build. You can also copy the file manually by using VisualGDB’s built-in SSH client in VS from Tools->SSH Host Manager by opening a console to the Raspberry Pi connection and using the SCP menu there.
Also, if you are using the cross-toolchain, then the executable is already on the Windows machine in the project’s directory.
Usually please contact our support directly with your order details to deactivate old unused seat activations.
We have currently looked up your license based on your name, you may activate again on another PC using your license key.
Hi,
When importing VisualGDB only looks in the standard directories for the source files. You can add the source files to the project manually after the project has been created.
The error in the wizard indicates that the project will not build with the current default settings. This error usually appears if you had NDK_MODULE_PATH defined for your project. You should specify NDK_MODULE_PATH as an additional argument to ndk-build on the Build settings page in VisualGDB Project Properties after you have created the project. You can see the entire build error message in the Output tool window in Visual Studio when building your project (after you have added all the source and header files to it).
Hi,
What kind of project do you have? Is it a Qt project and you are trying to add new GUI elements? If yes, then you can download the official Qt Visual Studio add-in in addition to VisualGDB to use a graphical editor to edit the GUI elements. You can find the add-in under “Other Downloads” from the following link: https://www.qt.io/download-open-source/
Hi,
Which exact error are you getting? The post you linked shows a failure in automatically installing Qt5 on Raspberry Pi.
As there is no official Qt5 package available on Raspberry Pi you are still expected to manually install Qt5. As you have already installed Qt5 manually based on the steps above that you yourself provided, VisualGDB should understand that Qt5 is installed and not offer to install it. The fix in VisualGDB is for setting up cross-compilation properly once Qt5 is already installed.
Hi,
We have published a fixed VisualGDB 4.3r3 version. Please try creating a new Qt5 cross-toolchain project with it as well as reconfiguring Qt5 cross-compilation in the project wizard to see if the fix works for you. Feel free to contact our sales if you need a trial extension.
If you are using a previously installed MinGW Qt5 toolchain to configure Qt5 cross-compilation, then please note that the version of the toolchain should match as closely as possible to the Qt5 version on the Raspberry Pi. We have successfully tested configuring cross-compilation with the Qt 5.4.0 MinGW toolchain.
Please note that due to a known bug, you must use a recent gcc 4.9.x version for both on the Raspberry Pi and for the cross-toolchain to be able to build projects using Qt5. A recent gcc version 4.9.x Raspberry Pi cross-toolchain can be downloaded from our website.
Hi,
Thank you for the kind words.
SmarTTY can also be launched from Tools->SSH Host Manager for your created connections in VisualGDB (Open console).
Alternatively to the embedded SmarTTY in VisualGDB there is also a standalone SmarTTY that can also be installed from http://smartty.sysprogs.com/ .Hi,
Thank you for the detailed steps to reproduce the issue. We have managed to recreate the issue and are currently looking at possible fixes. We will get back to you as soon as we have a fixed build for you to try.
Normally, the toolchain test does provide the error messages gathered during the test. In this case the error occurs in an unexpected location, we will add this error type to the log as well. Please note that it is always an option to ignore the toolchain test errors and to create the project anyway. This allows to see the full build logs and to customize the build commands.
Hi,
Ui::MainWindow is usually defined in the ui_MainWindow.h file that is generated during compilation.
Do you have such a file in the Debug subdirectory of your project directory? What are the file’s contents?
Additionally could you please post the full build output from the Output window here? Please rebuild the project before to ensure the log will be complete.
