Builds runs on one Pi 4 and not two others.

Sysprogs forums Forums VisualGDB Builds runs on one Pi 4 and not two others.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #29420
    richardf
    Participant

    I have reported this issue a while ago.

    I have three identical Pi 4.  I am running Visual Studio Community 2019 and VisualGDB 5.5R2 (although this happened before).  I can build and run on pi$bblack yet can’t build on pi$ablack (although it did build a few months ago).

    As I recall, back then, I rebuilt the project from scratch and it worked, yet the problem is back.

    Same code.  See file.

    Help.

     

     

    Attachments:
    You must be logged in to view attached files.
    #29424
    support
    Keymaster

    Hi,

    It looks like the target board is missing the ninja tool that is used to check dependencies and rebuild out-of-date files without any extra network delays. You can install ninja by running “sudo apt install ninja” on Raspberry Pi, or by creating another MSBuild-based project targeting that device from scratch, so that VisualGDB could recheck and install the required tools.

    #29436
    richardf
    Participant

    rm -rf “/tmp/VisualGDB/c/RaspGlo/GloR/VisualGDB/Debug”
    C:\RaspGlo\GloR => /tmp/VisualGDB/c/RaspGlo/GloR: 147 files copied (686KB).
    ninja -f “VisualGDB/Debug/GloR.msbuild-ninja”
    bash: ninja: command not found
    ————————————————————-
    Command exited with code 127
    Executable: ninja
    Arguments: -f “VisualGDB/Debug/GloR.msbuild-ninja”
    Directory: /tmp/VisualGDB/c/RaspGlo/GloR
    Command-line action failed

    ========== Project Rebuild Summary ==========
    GloR rebuilt in 00:00
    ========== Rebuild: 0 Succeeded, 1 Failed, 0 Skipped ==========

     

    I performed sudo apt install ninja. I rebooted.  I am logged in as pi.

    If I type ninja I get

    pi@ablack:~ $ ninja
    log: warning: no configuration file specified, using default values
    log: ninja version 0.1.3 initializing
    die: error: must run as root

    I can build and run successfully using GNU make except it is painfully slow.

    thanks

    #29437
    richardf
    Participant

    I then built an ap from start. When I try to build, I get:

    rm -rf “/tmp/VisualGDB/c/RaspberryPi/RaspAps/LinuxProject1/VisualGDB/Debug”
    C:\RaspberryPi\RaspAps\LinuxProject1 => /tmp/VisualGDB/c/RaspberryPi/RaspAps/LinuxProject1: 1 files copied (253 bytes).
    ninja -f “VisualGDB/Debug/LinuxProject1.msbuild-ninja”
    log: ninja version 0.1.3 initializing
    die: error: must run as root
    ————————————————————-
    Command exited with code 1
    Executable: ninja
    Arguments: -f “VisualGDB/Debug/LinuxProject1.msbuild-ninja”
    Directory: /tmp/VisualGDB/c/RaspberryPi/RaspAps/LinuxProject1
    Command-line action failed

    ========== Project Rebuild Summary ==========
    LinuxProject1 rebuilt in 00:02
    ========== Rebuild: 0 Succeeded, 1 Failed, 0 Skipped ==========

    #29445
    richardf
    Participant

    I build a simple ap from start. When I try to build on one of my Raspberry pi’s, I get:

    rm -rf “/tmp/VisualGDB/c/RaspberryPi/RaspAps/LinuxProject1/VisualGDB/Debug”
    C:\RaspberryPi\RaspAps\LinuxProject1 => /tmp/VisualGDB/c/RaspberryPi/RaspAps/LinuxProject1: 1 files copied (253 bytes).
    ninja -f “VisualGDB/Debug/LinuxProject1.msbuild-ninja”
    log: ninja version 0.1.3 initializing
    die: error: must run as root
    ————————————————————-
    Command exited with code 1
    Executable: ninja
    Arguments: -f “VisualGDB/Debug/LinuxProject1.msbuild-ninja”
    Directory: /tmp/VisualGDB/c/RaspberryPi/RaspAps/LinuxProject1
    Command-line action failed

    #29447
    support
    Keymaster

    Hi,

    As the message suggests, ninja expects to be run as root on Raspberry Pi.

    You can configure Raspberry Pi to permit root logins as shown here and then create another SSH connection in the VisualGDB wizard or project properties (root@raspberrypi instead of pi@raspberrypi).

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.