COMMAND-LINE ACTION FAILED

Sysprogs forums Forums VisualGDB COMMAND-LINE ACTION FAILED

Tagged: 

This topic contains 8 replies, has 2 voices, and was last updated by  support 1 month, 2 weeks ago.

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #25520

    jyurig
    Participant

    Hi,

    I open that already worked on another computer sometime before and I trying to build it in visual studio and I get this error:

    Severity Code Description Project File Line Suppression State
    Error Command-line action failed “name of the project” C:\Users\…\VisualGDB 1

    How do I fix this error?

    Thanks

     

     

    Attachments:
    You must be logged in to view attached files.
    #25522

    support
    Keymaster

    Hi,

    Sorry, but the only way to tell what is going on is to check the View->Output window as suggested by the second error message on the screenshot. It will show the detailed build log that should point to a specific part of the build that failed.

    #25528

    jyurig
    Participant
    • This reply was modified 1 month, 3 weeks ago by  support. Reason: formatting
    #25543

    support
    Keymaster

    Hi,

    It looks like the project has some leftovers from the previous BSP version, or previous configuration. Please try rebuilding it via Build->Rebuild All.

    #25553

    jyurig
    Participant

    it’s doing the same but without ignoring old recipe.

    #25554

    support
    Keymaster

    No problem. We can help you track it down, however we would first kindly ask you to renew your license and update to the latest VisualGDB 5.4 as the issue you have might be specific to an older VisualGDB version.

    #25562

    jyurig
    Participant

    I do have version 5.4.111.3235.

    About renewing the license, we will do it soon, I just need to justify it by showing its work with visualGDB.

    #25563

    support
    Keymaster

    No problem. As soon as you renew your license, we should be able to help you further.

    #25586

    support
    Keymaster

    Thank you for renewing your license.
    The error message you reported looks like the project references the system_nrf51.c file that is no longer present in the latest BSP.
    Nordic has removed nRF51 support (only leaving out nRF52) in the latest SDK versions, so our BSPs had to follow.
    As a workaround, we have released a separate BSP supporting the legacy nRF51 device using the latest BSP version that supports it.

    The recommended way to proceed with this would be to create a new project for the nRF51 device using MSBuild (GNU Make may not be compatible with the latest Nordic SDKs due to path length limitations) and moving the code to it. It would require additional setup, however omce the code is moved over, you will get much faster building experience than with GNU Make and also better integration with VS property windows.
    We can also show you how to patch the existing project definition to have it retargeted to the special nRF51 BSP, however it may not work with GNU Make due to path length limitations.

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.