In this mode VisualGDB will keep a local copy of all source files in the project directory and will upload the modified ones before you begin debugging: Proceed with the default file synchronization settings.If you are using version 5.3 or earlier, you may need to specify the Python header directory manually. If you are using VisualGDB 5.4 or later, it will automatically detect Python-related settings and check that all the necessary components are present. If you have the pre-packaged Python installed as well, we recommend entering the full path to avoid confusion: On the next page enter “python3” or the full path to the installed Python executable in the “Python executable” field.On the next page click “Build the project under Linux” and select your Raspberry Pi in the “Remote computer” field:.On the first page of the wizard select the Python-based project:.Start Visual Studio and open VisualGDB Linux Project Wizard:.You can double-check this by running “which python3” followed by “python3 –version”: The Python executable will normally be installed under /usr/local/bin.In order to add an extra index globally on your system, all you need to do is edit (or create) a file /etc/pip.conf with the following contents: Īfter that, you should see something like: $ pip3 install numpy=1.17.1 To solve that, I would recommend adding as an extra index for packages so that you can obtain pre-compiled wheels on your Raspberry Pi, saving you a lot of time.
This will give you a better understanding of the problem you are seeing. To see what is happening under the hood, you can run pip3 with -verbose. The long delay is because numpy is being compiled on your Raspberry Pi.
0 kommentar(er)
