support

Forum Replies Created

Viewing 15 posts - 5,731 through 5,745 (of 7,512 total)
  • Author
    Posts
  • in reply to: Source path outside project directory. #9130
    support
    Keymaster

    Hi,

    You can add a custom file transfer to pre-build actions via VisualGDB Project Properties (requires Custom edition or higher) or simply change the local source directory on the Project Settings page to the parent directory that contains both your Makefile directory and the source file directories.

    in reply to: OpenCV link error #9125
    support
    Keymaster

    Based on your build log, it looks like VisualGDB is not passing the toolchain definition to CMake. Normally the build command should look like this:

    1>  VisualGDB: Run "C:\Program Files (x86)\CMake\bin\cmake.exe -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_COLOR_MAKEFILE=OFF .. -DCMAKE_TOOLCHAIN_FILE=toolchain-Debug.cmake -DCMAKE_MAKE_PROGRAM="C:/SysGCC/raspberry/bin/make.exe"" in directory "c:\projects\LinuxProject8/Debug" on local computer

    Note the -DCMAKE_TOOLCHAIN_FILE part. Please try creating your VisualGDB project again and double-check that you select the correct cross-toolchain in the project wizard.

    in reply to: prebuild action is always in background mode #9124
    support
    Keymaster

    Hi,

    This is indeed a bug, thanks for reporting it. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.10.1169.msi

     

    in reply to: Debugging shared library #9123
    support
    Keymaster

    Hi,

    Our best guess is that the library is built using a different compiler (e.g. using native g++ instead of a cross-compiler for your ARM board). You can check that by running “readelf -h <file>” for the main application and the .so file. If the “Machine” field is mismatching, please double-check the compiler you are using.

    in reply to: how do I setup VisualGDB for Nucleo F091RC? #9122
    support
    Keymaster

    Hi,

    Most likely your firewall has blocked VisualGDB from downloading the project templates automatically.
    Please try downloading them manually here: http://visualgdb.com/hwsupport/
    You can install them via Tools->VisualGDB Package Manager (v5.2) or Embedded Tools Manager (v5.1).

    in reply to: error VGDB1002 #9118
    support
    Keymaster

    Hi,

    The ‘U’ in front of the symbol means that the symbol is undefined, hence the RevLibApi.o file expects some other file to define RevLib::RevLibObject::GetInstance().

    Please check your source files for the definition (not declaration) of RevLib::RevLibObject::GetInstance() and then check the corresponding .o file.

    in reply to: Intellisense settings for multiple targets are being deleted #9115
    support
    Keymaster

    Hi,

    This is somewhat of a limitation of the way VisualGDB stores the remote directories. As they can be different for different hosts anyway, we would recommend opening the Makefile Settings page of VisualGDB Project Properties, changing something there (e.g. adding and removing space to CFLAGS) and pressing ‘Apply’. This will automatically redetect and re-configure the IntelliSense directories.

    You can also try our new MSBuild backend in VisualGDB 5.2 (currently in Beta). It has a more automated way of dealing with remote include directories (you will still need to to click “repair MSBuild settings” after you change the alias target).

    in reply to: OpenCV link error #9114
    support
    Keymaster

    Looks like the Raspicam library is picking up the Windows build of OpenCV.
    If you want to use it with OpenCV, please consider following this tutorial for build it for Raspberry Pi. If not, please edit the CMakeLists.txt of the raspicam library to remove references to OpenCV.

    The step 22 looks different because you have created your main project with CMake, not GNU Make. Both should work though, so it should not be a problem.

    in reply to: error VGDB1002 #9111
    support
    Keymaster

    Hi,

    Looks like your library somehow ended up missing those method definitions. According to your build log, your application is linked against the library:

    g++ -o LinuxConApp/RevLibConApp -Wl,-gc-sections -Wl,--start-group LinuxConApp/main.o LinuxConApp/ProgressMonitor.o LinuxConApp/RevLibTest.o ../RevLib/wrk/LinuxConApp/RevLib.so -Wl,--rpath='$ORIGIN' -Wl,--rpath='$ORIGIN/../../RevLib/wrk/LinuxConApp/' -Wl,--end-group

    You can check the list of functions exported from a library by running the following command on the Linux side:

    nm <full path to .so file> | c++filt

    If it does not mention anything similar to RevLib::GetRevLibObjectInterface(), please locate the .cpp file that defines it, find a matching .o file on your Linux side and run ‘nm’ on it. If the .o file does not contain the method, please double-check your source code. If the .o file does not exist, please double-check the Library Makefile.

    in reply to: How to use .so file? #9086
    support
    Keymaster

    Hi,

    Normally all you need to do is add a reference to the .so project in the properties of your main project (right-click in Solution Explorer, Add Reference).

    in reply to: Latest STM32 BSP 3.7r2 #9085
    support
    Keymaster

    Hi,

    Yes, you can always download the older BSPs here: http://visualgdb.com/hwsupport/

    Normally though a BSP upgrade should not affect stand-alone projects (you can try simply renaming the BSP directory and confirming that the project still builds), so perhaps the upgrade coincided with something else?

    support
    Keymaster

    Hi,

    Thanks very much for sharing this, it is indeed a VisualGDB bug. We have fixed it in this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.8.1132.msi

    Please open your VisualGDB Project Properties and change the Include Directories field arbitrarily (e.g. add and remove a space), then press OK. VisualGDB will then update the CMakeLists.txt correctly.

    support
    Keymaster

    Hi,

    According to your log, there are 2 definitions of the posix_memalign() function:

    1. C:\Users\akhils\AppData\Local\VisualGDB\RemoteSourceCache\192.168.0.54\0001\include\mm_malloc.h(34,64)
    2. C:\Users\akhils\AppData\Local\VisualGDB\RemoteSourceCache\192.168.0.54\0000\include\stdlib.h(503,12)

    This normally means that your system is too old and does not support C++11 properly. You can try patching the headers to have matching definitions at your own risk, but you may encounter further problems with C++11 on that system.

    in reply to: compiler and library support for the ISO C++ 2011 standard #9075
    support
    Keymaster

    Hi,

    This one can be safely ignored and should be solved in the upcoming Beta 1.

    If everything else works, we would recommend simply updating to Beta 1 once it is released.

    in reply to: Cannot Connect #9074
    support
    Keymaster

    Hi,

    The “127.0.0.1” address always refers to the “current machine”, so if you try to connect to 127.0.0.1 from VisualGDB, it will try to connect to the Windows machine itself and will not work. Please use the “ifconfig” command on the Linux machine to find our its actual IP address and use it instead. Please also ensure that your VM network settings are configured in a way that allows the two machine to communicate with each other (e.g. bridged connection to your local network).

Viewing 15 posts - 5,731 through 5,745 (of 7,512 total)