Forum Replies Created
-
Posts
-
Hi,
You can easily add custom pre-build actions that will transfer any header files (or whole directories) to Raspberry Pi (see the Build Customization page of VisualGDB Project Properties). Then simply ensure that the relative paths to the directories where the headers end up are specified on your Build Settings page and you should be able to build the project successfully.
Hi,
VisualGDB actually recognizes and substitutes the normal environment variables with the $(Variable) syntax. Hence you can simply use the $(USERNAME) syntax to refer to the built-in Windows variable containing the current user name.
OK, we’ve fixed this. Please update your Segger debug package to version 3.3. We have added a new more reliable live memory engine based on the feedback from Segger.
Note that it’s somewhat slower than the old one, so we have also added an option that allows switching between the old and the new one. Let us know if this solves the problem.
Hi,
VisualGDB does not automatically configure the Python IntelliSense to match your Raspberry Pi. However you can configure it fairly easily:
- Open Tools->Python Tools->Python Environments
- Find the default environment there
- Create a copy of your Python directory used by the default environment and copy the packages from Raspberry Pi to that copy so that they don’t interfere with your regular Python installation
- Edit the Python environment settings in VS to use the new Python directory
This should get IntelliSense to display the libraries copied from Raspberry Pi.
Hi,
Yes, it sometimes causes Make to simply hang. VisualGDB 5.2 will come with a separate MSBuild platform that will integrate the existing toolchains directly into the Visual Studio build system, so the multi-threaded build will be automatic and it won’t trigger the Make bug.
Hi,
Looks like you have a typo in the MCUDefinitionFile element:
<MCUDefinitionFile>\device\nRF52.xml</MCUDefinitionFile>
According to Windows path syntax, this actually means X:\device\nRF52.xml, where X: is the drive letter of the project directory. Please try changing it to this:
<MCUDefinitionFile>device\nRF52.xml</MCUDefinitionFile>
Hi,
We are planning to update our mbed package after we release VisualGDB 5.2 Beta 1. The current plan is to do this by the end of September.
Hi,
Yes, you can disable this, although it will require some minor XML editing. Please try removing the ‘DownloadableSourcePackage’ elements from the toolchain.xml file in your toolchain directory.
Yes, we got all the necessary information from Segger and are expecting to release an update next week.
First of all, could you try debugging your existing ELF file with the Quick Debug feature? If this does not work, could you please attach the contents of the Segger J-Link window and the GDB Session window (switch view to ‘All GDB interaction’ so that we could see the internally sent commands)? This should explain what is going on.
Hi,
Yes, it is possible to configure IntelliSense to show the imported code, however could you first clarify if you mean Python IntelliSense or C++ IntelliSense?
Hi,
Sorry about that. You should be able to click “ignore” to get past the error message and get the project created. Then you can send us the project and we should be able to tell you what is going wrong with it.
Regarding the “command not found”, most likely you have specified an incorrect path when importing the toolchain. We normally recommend using the toolchains that VisualGDB itself downloads installs as they are tested to work out-of-the-box.
Hi,
Yes, the settings on the “General, Scroll Bars and Tabs” pages do not get synchronized automatically due to the internal architecture of the VS language services. However all the advanced code formatting settings (from the Formatting pages) should get synchronized properly.
Regarding Makefile, the EXTERNAL_LIBS variable is meant to be automatically updated by VisualGDB based on the referenced projects. If you want to manually add libraries that are not otherwise references, please use the ADDITIONAL_LINKER_INPUTS variable.
Hi,
Wow, that would be quite complex actually. Delphi uses the Pascal programming language and the VCL library, while making GUI for Raspberry Pi typically involves C++ and the Qt library, that are completely different.
You would essentially need to develop the Raspberry Pi version from scratch and use the Delphi version as your reference. If you don’t have software development experience to do this yourself, we could offer you our consulting services to have this done for you. You can simply contact sales@sysprogs.com with a brief overview of your application so that we could get you a basic estimate.
