Multiple definitions of source files

Sysprogs forums Forums VisualGDB Multiple definitions of source files

This topic contains 23 replies, has 2 voices, and was last updated by  support 7 hours, 34 minutes ago.

Viewing 9 posts - 16 through 24 (of 24 total)
  • Author
    Posts
  • #22465

    support
    Keymaster

    Hi,

    Just wanted to let you know that we have updated VisualGDB to run the Cygwin build of CMake using an alternate mechanism that does not trigger the problem. Please use this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.7.2524.msi

    It also looks like as of v3.12, the Cygwin-based build of CMake would crash when trying to reload a project without restarting it:

    If you ever encounter that message, please right-click on the project in Solution Explorer and select “Reload CMake Project”. This will restart CMake and reload the project successfully.

    #22516

    salex
    Participant

    Hello,

    It seems that i missed the link you posted, it is already unavailable.

    Please let me download it again.

     

    #22517

    support
    Keymaster

    Hi,

    Sorry about that. Please download v5.4 Preview 8. It includes all the fixes from all previous builds.

    #22558

    salex
    Participant

    Hello,

    I’ve installed the v5.4 Preview 8.

    I succeeded to load the project without errors.

    The problem you mentioned happens every time i try to build the project.

    On the build command i get following message:

    Code model queried in 1483 msec
    assertion “0” failed: file “/home/salex/CMake/Utilities/cmlibuv/src/unix/core.c”, line 185, function: uv_close
    1 [main] cmake 47776 cygwin_exception::open_stackdumpfile: Dumping stack trace to cmake.exe.stackdump
    Unexpected JSON message: expected Reply, got
    System.Exception: Unexpected JSON message: expected Reply, got
    at go1.m1[_InType,_OutType](_InType a)
    at y22.m(String[] a)
    at y22.x1(Hello a)
    at go1.e()
    CMake exited with code 34304
    System.Exception: CMake exited with code 34304
    at v3.l(Object a, EventArgs b)

    On rebuild command i got following message:

    —— Build started: Project: Px4_WinGDB.vgdbcmake (failed), Configuration: Debug VisualGDB ——
    VisualGDB: Run “C:\PX4\toolchain\cygwin64\bin\bash.exe -c “C:\PX4\toolchain\cygwin64\bin\cmake.exe ../.. -G \”Unix Makefiles\” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_COLOR_MAKEFILE=OFF -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DTOOLCHAIN_ROOT=C:/PX4/toolchain/cygwin64″” in directory “/cygdrive/c/PX4/home/Firmware/VisualGDB/Debug” on local computer
    /usr/bin/bash: C:PX4toolchaincygwin64bincmake.exe: command not found
    ————————————————————-
    Command exited with code 127
    Executable: C:\PX4\toolchain\cygwin64\bin\bash.exe
    Arguments: -c “C:\PX4\toolchain\cygwin64\bin\cmake.exe ../.. -G \”Unix Makefiles\” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_COLOR_MAKEFILE=OFF -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DTOOLCHAIN_ROOT=C:/PX4/toolchain/cygwin64″
    Directory: /cygdrive/c/PX4/home/Firmware/VisualGDB/Debug
    VisualGDB: Error: Command-line action failed

     

    #22564

    support
    Keymaster

    Hi,

    No problem, we can add a workaround to the first problem that will automatically restart CMake if it crashes during reconfiguration.

    The second problem looks like you are using backward slashes in the path to GNU Make (configured via VisualGDB Project Properties). Please try using forward slashes instead and let us know if this solves the problem.

    #22588

    salex
    Participant

    Ok,
    I’m waiting for the fix.

    #22608

    support
    Keymaster

    Hi,

    No problem. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.9.2552.msi

    #22668

    salex
    Participant

    Hi,

    This version one is working. It started to build the program.

    The next problem is that the VisualGDB executes bash.exe of Cygwin without login option.

    VisualGDB: Run “C:\PX4\toolchain\cygwin64\bin\bash.exe -c “make “” in directory “c:\PX4\home\Firmware\VisualGDB\Debug” on local computer

    This causes that some python scripts, which are activated from the CMakeList, cannot import modules (numpy).

    I tried manually to do this, and bash.exe -l , should solve the problem.

    Can i add this option in configuration, or the command is hard-coded in VisualGDB ?

     

    #22695

    support
    Keymaster

     

    Hi,

    Yes, you should be able to customize the build command line via VisualGDB Project Properties -> CMake project settings -> Make Command.

Viewing 9 posts - 16 through 24 (of 24 total)

You must be logged in to reply to this topic.