Troubles in compiling pc-ble-driver v4.1.2 for Python project with nRF52840 dongle

[Fabio Ballanti]

Hi,

As many of you, I'm tryng to compile pc-ble-driver (v4.1.2) found in https://github.com/NordicSemiconductor/pc-ble-driver/tree/v4.1.2, just to see how the code works and to re-use some parts in a Python project that I'm developing using the nRF52840 Dongle.

The Operative System is Windows 10 64-bit.

I've completed successfully the following steps Driver installation, Driver validation, Installing tools, Installing dependencies until facing troubles in Compiling pc-ble-driver on Windows:

- First problem encountered when Installing vcpkg dependencies: from the System Environment, I had to delete VCPKG_ROOT variable (previously set in the step 5 of Installing dependencies on Windows) and leave only the vcpkg correct link in path variable; after that I was able to install the vcpkg dependencies

mkdir build
cd build
vcpkg install asio
vcpkg install catch2
vcpkg install --head spdlog

- Second problem encountered at point "CMake Select the Visual Studio compiler to use according to this article: Build C/C++ code on the command line": (here I'm asking if someone can help me)

in this section, the System Environment variables CC and CXX were set  for MSVC compiler, and the cmake answer is as follow:

PS C:\Users\Fabio\Documents\nRF52840_Dongle\pc-ble-driver-4.1.2\build> cmake -G Ninja ..
-- NRF_BLE_DRIVER_VERSION not specified, setting it to 0.0.0
-- CONNECTIVITY_VERSION not specified, setting it to 0.0.0
-- The C compiler identification is MSVC 19.27.29112.0
-- The CXX compiler identification is MSVC 19.27.29112.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.27.29110/bin/Hostx86/x86/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.27.29110/bin/Hostx86/x86/cl.exe - broken
CMake Error at C:/Program Files/CMake/share/cmake-3.18/Modules/CMakeTestCCompiler.cmake:66 (message):
  The C compiler

    "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.27.29110/bin/Hostx86/x86/cl.exe"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: C:/Users/Fabio/Documents/nRF52840_Dongle/pc-ble-driver-4.1.2/build/CMakeFiles/CMakeTmp

    Run Build Command(s):C:/ProgramData/chocolatey/bin/ninja.exe cmTC_23be1 && [1/2] Building C object CMakeFiles\cmTC_23be1.dir\testCCompiler.c.obj
    [2/2] Linking C executable cmTC_23be1.exe
    FAILED: cmTC_23be1.exe
    cmd.exe /C "cd . && "C:\Program Files\CMake\bin\cmake.exe" -E vs_link_exe --intdir=CMakeFiles\cmTC_23be1.dir --rc=rc --mt=CMAKE_MT-NOTFOUND --manifests  -- C:\PROGRA~2\MICROS~2\2019\COMMUN~1\VC\Tools\MSVC\1427~1.291\bin\Hostx86\x86\link.exe /nologo CMakeFiles\cmTC_23be1.dir\testCCompiler.c.obj  /out:cmTC_23be1.exe /implib:cmTC_23be1.lib /pdb:cmTC_23be1.pdb /version:0.0 /machine:X86  /debug /INCREMENTAL /subsystem:console  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cmd.exe /C "cd /D C:\Users\Fabio\Documents\nRF52840_Dongle\pc-ble-driver-4.1.2\build\CMakeFiles\CMakeTmp && powershell -noprofile -executionpolicy Bypass -file C:/src/vcpkg/scripts/buildsystems/msbuild/applocal.ps1 -targetBinary C:/Users/Fabio/Documents/nRF52840_Dongle/pc-ble-driver-4.1.2/build/CMakeFiles/CMakeTmp/cmTC_23be1.exe -installedDir C:/src/vcpkg/installed/x86-windows/debug/bin -OutVariable out""
    RC Pass 1: command "rc /fo CMakeFiles\cmTC_23be1.dir/manifest.res CMakeFiles\cmTC_23be1.dir/manifest.rc" failed (exit code 0) with the following output:
    The system cannot find the file specified
    ninja: build stopped: subcommand failed.





  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:25 (project)


-- Configuring incomplete, errors occurred!
See also "C:/Users/Fabio/Documents/nRF52840_Dongle/pc-ble-driver-4.1.2/build/CMakeFiles/CMakeOutput.log".
See also "C:/Users/Fabio/Documents/nRF52840_Dongle/pc-ble-driver-4.1.2/build/CMakeFiles/CMakeError.log".
PS C:\Users\Fabio\Documents\nRF52840_Dongle\pc-ble-driver-4.1.2\build>

So, long story short, I'm blocked: Can any one please help me?

P.S. As a completion, but don't think is part of the problem, "gcc-arm-none-eabi-9-2020-q2-update-win32" was installed and 

 the `Mass Storage Device` was disable (using regedit ), as described in Driver installation

Thank you.

Fabio

[Karl Ylvisaker]

Hello Fabio,

This seems to be an issue with your cmake configuration and c compiler, rather than a problem with the pc-ble-driver.

I've completed successfully the following steps Driver installation, Driver validation, Installing tools, Installing dependencies until facing troubles in Compiling pc-ble-driver on Windows:

Could you tell me, do you intend to use the pc-ble-driver, or the pc-ble-driver-py? From the title of your ticket, I assume you would like to use the pc-ble-driver-py. If this is the case, please follow its specific installation guide, from the main repository readme.
If you are intending to use the pc-ble-driver, we will continue with the debug of the above: Could you then list the specific steps ( with commands, if possible ) that you used to get to this error in the installation? Ideally, if you create it as a .bat file with the commands I can attempt to replicate it in a mint virtual Windows machine, to easier debug the issue. Alternatively, if you could list the tutorial steps that you followed ( and which tutorial you followed, in which order ), that is also an alternative.

Looking forward to resolving this issue together!

Best regards,
Karl

[Fabio Ballanti]

Hello Karl,

Yes, I will also try pc-ble-driver-py as you recommended (and probably write a Q&A for that):

Karl Ylvisaker said:

please follow its specific installation guide, from the main repository readme.

But for the moment, let's proceed with pc-ble-driver v4.1.2.

For me it's more simple writing you the steps and the code used as reported in Git Hub at NordicSemiconductor/pc-ble-driver, using Power Shell:

STEP 1 - Driver Installation and Driver Validation as reported here

STEP 2 - Installing Tools as reported here 

STEP 3 - Installing dependencies on Windows as reported here: 

• Download Visual Studio 15 or later version and install.(in this step I've installed even Visual Studio 2015 and Visual Studio 2019)
• Install Chocolatey. Install with cmd.exe (Run as administrator)

Using Power Shell launch the following commands:

PS C:\WINDOWS\system32>  Get-ExecutionPolicy
AllSigned
PS C:\WINDOWS\system32> Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))

Then add the Chocolatey location to the PATH

• Install Git.

PS C:\WINDOWS\system32> choco install -y git  

• Install CMake.

PS C:\WINDOWS\system32> choco install -y cmake

Then add the CMake location to the PATH

• Install vcpkg.

PS C:\WINDOWS\system32> cd ..
PS C:\WINDOWS> cd ..
PS C:\> git clone https://github.com/Microsoft/vcpkg.git
PS C:\> cd vcpkg
PS C:\vcpkg> git checkout tags/2020.04
PS C:\vcpkg> .\bootstrap-vcpkg.bat

Then add the vcpkg location to the PATH

Fabio Ballanti said:

leave only the vcpkg correct link in path variable

STEP 4 - As described on the GitHub page, those steps are needed only if you want to compile your own connectivity HEX files

• Install ninja.

PS C:\> choco install -y ninja

• Download and install GNU Embedded Toolchain for Arm here

Then add the location in the Environment Variable GNUARMEMB_TOOLCHAIN_PATH 

• Install Python and pip, and then install nrfutil

PS C:\> pip install nrfutil

STEP 5 - Compiling pc-ble-driver from source

• Install vcpkg dependencies.

PS C:\> cd C:\nRF52840_Dongle\pc-ble-driver-4.1.2
PS C:\nRF52840_Dongle\pc-ble-drive-4.1.2r> mkdir build
PS C:\nRF52840_Dongle\pc-ble-driver-4.1.2> cd build
PS C:\nRF52840_Dongle\pc-ble-driver-4.1.2\build> vcpkg install asio
PS C:\nRF52840_Dongle\pc-ble-driver-4.1.2\build> vcpkg install catch2
PS C:\nRF52840_Dongle\pc-ble-driver-4.1.2\build> vcpkg install --head spdlog

• CMake Select the Visual Studio compiler to use according to this article: Build C/C++ code on the command line

Fabio Ballanti said:

in this section, the System Environment variables CC and CXX were set  for MSVC compiler

PS C:\nRF52840_Dongle\pc-ble-driver-4.1.2\build> cmake -G Ninja ..

At this point I've encountered the problem described above...

Thank you!

Regards,

Fabio

[Karl Ylvisaker]

Hello Fabio,

Thank you for the very detailed walkthrough of your installation! - it is very helpful for me when debugging this.

Fabio Ballanti said:

Yes, I will also try pc-ble-driver-py as you recommended (and probably write a Q&A for that):

Great! That is a sound plan.

Fabio Ballanti said:

At this point I've encountered the problem described above...

A couple of questions to rule out some common pitfalls:
- Did you complete the Download and install the tools section of the Microsoft documentation, referenced in step 5?
- Could you run the following command in your PowerShell, and let me know what it outputs:  

cmake --version

If you could also run the following command, and copy-paste the contents of the "Generators" section, that would be helpful as well:

cmake --help

This might seem trivial, but having seen these outputs will help me in narrowing down the issue.
- Could you also share with me your system PATH and variables you have added to it? You mentioned earlier that you had to delete the vcpkg variable to be able to install the vcpkg dependencies - this sounds strange.

Looking forward to resolving this issue together!

Best regards,
Karl

[Fabio Ballanti]

Hello Karl,

Karl Ylvisaker said:

- Did you complete the Download and install the tools section of the Microsoft documentation, referenced in step 5?

Yes, I did.

Karl Ylvisaker said:

- Could you run the following command in your PowerShell, and let me know what it outputs: 

Here you'll find the outputs for cmake --version and cmake --help

PS C:\WINDOWS\system32> cmake --version
cmake version 3.18.4

CMake suite maintained and supported by Kitware (kitware.com/cmake).
PS C:\WINDOWS\system32> cmake --help
Usage

  cmake [options] <path-to-source>
  cmake [options] <path-to-existing-build>
  cmake [options] -S <path-to-source> -B <path-to-build>

Specify a source directory to (re-)generate a build system for it in the
current working directory.  Specify an existing build directory to
re-generate its build system.

Options
  -S <path-to-source>          = Explicitly specify a source directory.
  -B <path-to-build>           = Explicitly specify a build directory.
  -C <initial-cache>           = Pre-load a script to populate the cache.
  -D <var>[:<type>]=<value>    = Create or update a cmake cache entry.
  -U <globbing_expr>           = Remove matching entries from CMake cache.
  -G <generator-name>          = Specify a build system generator.
  -T <toolset-name>            = Specify toolset name if supported by
                                 generator.
  -A <platform-name>           = Specify platform name if supported by
                                 generator.
  -Wdev                        = Enable developer warnings.
  -Wno-dev                     = Suppress developer warnings.
  -Werror=dev                  = Make developer warnings errors.
  -Wno-error=dev               = Make developer warnings not errors.
  -Wdeprecated                 = Enable deprecation warnings.
  -Wno-deprecated              = Suppress deprecation warnings.
  -Werror=deprecated           = Make deprecated macro and function warnings
                                 errors.
  -Wno-error=deprecated        = Make deprecated macro and function warnings
                                 not errors.
  -E                           = CMake command mode.
  -L[A][H]                     = List non-advanced cached variables.
  --build <dir>                = Build a CMake-generated project binary tree.
  --install <dir>              = Install a CMake-generated project binary
                                 tree.
  --open <dir>                 = Open generated project in the associated
                                 application.
  -N                           = View mode only.
  -P <file>                    = Process script mode.
  --find-package               = Run in pkg-config like mode.
  --graphviz=[file]            = Generate graphviz of dependencies, see
                                 CMakeGraphVizOptions.cmake for more.
  --system-information [file]  = Dump information about this system.
  --log-level=<ERROR|WARNING|NOTICE|STATUS|VERBOSE|DEBUG|TRACE>
                               = Set the verbosity of messages from CMake
                                 files.  --loglevel is also accepted for
                                 backward compatibility reasons.
  --log-context                = Prepend log messages with context, if given
  --debug-trycompile           = Do not delete the try_compile build tree.
                                 Only useful on one try_compile at a time.
  --debug-output               = Put cmake in a debug mode.
  --debug-find                 = Put cmake find in a debug mode.
  --trace                      = Put cmake in trace mode.
  --trace-expand               = Put cmake in trace mode with variable
                                 expansion.
  --trace-format=<human|json-v1>
                               = Set the output format of the trace.
  --trace-source=<file>        = Trace only this CMake file/module.  Multiple
                                 options allowed.
  --trace-redirect=<file>      = Redirect trace output to a file instead of
                                 stderr.
  --warn-uninitialized         = Warn about uninitialized values.
  --warn-unused-vars           = Warn about unused variables.
  --no-warn-unused-cli         = Don't warn about command line options.
  --check-system-vars          = Find problems with variable usage in system
                                 files.
  --profiling-format=<fmt>     = Output data for profiling CMake scripts.
                                 Supported formats: google-trace
  --profiling-output=<file>    = Select an output path for the profiling data
                                 enabled through --profiling-format.
  --help,-help,-usage,-h,-H,/? = Print usage information and exit.
  --version,-version,/V [<f>]  = Print version number and exit.
  --help-full [<f>]            = Print all help manuals and exit.
  --help-manual <man> [<f>]    = Print one help manual and exit.
  --help-manual-list [<f>]     = List help manuals available and exit.
  --help-command <cmd> [<f>]   = Print help for one command and exit.
  --help-command-list [<f>]    = List commands with help available and exit.
  --help-commands [<f>]        = Print cmake-commands manual and exit.
  --help-module <mod> [<f>]    = Print help for one module and exit.
  --help-module-list [<f>]     = List modules with help available and exit.
  --help-modules [<f>]         = Print cmake-modules manual and exit.
  --help-policy <cmp> [<f>]    = Print help for one policy and exit.
  --help-policy-list [<f>]     = List policies with help available and exit.
  --help-policies [<f>]        = Print cmake-policies manual and exit.
  --help-property <prop> [<f>] = Print help for one property and exit.
  --help-property-list [<f>]   = List properties with help available and
                                 exit.
  --help-properties [<f>]      = Print cmake-properties manual and exit.
  --help-variable var [<f>]    = Print help for one variable and exit.
  --help-variable-list [<f>]   = List variables with help available and exit.
  --help-variables [<f>]       = Print cmake-variables manual and exit.

Generators

The following generators are available on this platform (* marks default):
* Visual Studio 16 2019        = Generates Visual Studio 2019 project files.
                                 Use -A option to specify architecture.
  Visual Studio 15 2017 [arch] = Generates Visual Studio 2017 project files.
                                 Optional [arch] can be "Win64" or "ARM".
  Visual Studio 14 2015 [arch] = Generates Visual Studio 2015 project files.
                                 Optional [arch] can be "Win64" or "ARM".
  Visual Studio 12 2013 [arch] = Generates Visual Studio 2013 project files.
                                 Optional [arch] can be "Win64" or "ARM".
  Visual Studio 11 2012 [arch] = Generates Visual Studio 2012 project files.
                                 Optional [arch] can be "Win64" or "ARM".
  Visual Studio 10 2010 [arch] = Generates Visual Studio 2010 project files.
                                 Optional [arch] can be "Win64" or "IA64".
  Visual Studio 9 2008 [arch]  = Generates Visual Studio 2008 project files.
                                 Optional [arch] can be "Win64" or "IA64".
  Borland Makefiles            = Generates Borland makefiles.
  NMake Makefiles              = Generates NMake makefiles.
  NMake Makefiles JOM          = Generates JOM makefiles.
  MSYS Makefiles               = Generates MSYS makefiles.
  MinGW Makefiles              = Generates a make file for use with
                                 mingw32-make.
  Unix Makefiles               = Generates standard UNIX makefiles.
  Green Hills MULTI            = Generates Green Hills MULTI files
                                 (experimental, work-in-progress).
  Ninja                        = Generates build.ninja files.
  Ninja Multi-Config           = Generates build-<Config>.ninja files.
  Watcom WMake                 = Generates Watcom WMake makefiles.
  CodeBlocks - MinGW Makefiles = Generates CodeBlocks project files.
  CodeBlocks - NMake Makefiles = Generates CodeBlocks project files.
  CodeBlocks - NMake Makefiles JOM
                               = Generates CodeBlocks project files.
  CodeBlocks - Ninja           = Generates CodeBlocks project files.
  CodeBlocks - Unix Makefiles  = Generates CodeBlocks project files.
  CodeLite - MinGW Makefiles   = Generates CodeLite project files.
  CodeLite - NMake Makefiles   = Generates CodeLite project files.
  CodeLite - Ninja             = Generates CodeLite project files.
  CodeLite - Unix Makefiles    = Generates CodeLite project files.
  Sublime Text 2 - MinGW Makefiles
                               = Generates Sublime Text 2 project files.
  Sublime Text 2 - NMake Makefiles
                               = Generates Sublime Text 2 project files.
  Sublime Text 2 - Ninja       = Generates Sublime Text 2 project files.
  Sublime Text 2 - Unix Makefiles
                               = Generates Sublime Text 2 project files.
  Kate - MinGW Makefiles       = Generates Kate project files.
  Kate - NMake Makefiles       = Generates Kate project files.
  Kate - Ninja                 = Generates Kate project files.
  Kate - Unix Makefiles        = Generates Kate project files.
  Eclipse CDT4 - NMake Makefiles
                               = Generates Eclipse CDT 4.0 project files.
  Eclipse CDT4 - MinGW Makefiles
                               = Generates Eclipse CDT 4.0 project files.
  Eclipse CDT4 - Ninja         = Generates Eclipse CDT 4.0 project files.
  Eclipse CDT4 - Unix Makefiles= Generates Eclipse CDT 4.0 project files.

Karl Ylvisaker said:

- Could you also share with me your system PATH and variables you have added to it? You mentioned earlier that you had to delete the vcpkg variable to be able to install the vcpkg dependencies - this sounds strange.

Not properly: I've set only the vcpkg link in PATH: C:\src\vcpkg;

here the whole environment variables, launching "set" from Command Prompt:

ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\Fabio\AppData\Roaming
CC=C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.27.29110\bin\Hostx86\x86\cl.exe
ChocolateyInstall=C:\ProgramData\chocolatey
ChocolateyLastPathUpdate=132482091631219347
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=LAPTOP-5NFKIEGS
ComSpec=C:\WINDOWS\system32\cmd.exe
CXX=C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.27.29110\bin\Hostx86\x86\cl.exe
DASHLANE_DLL_DIR=C:\Users\Fabio\AppData\Roaming\Dashlane\6.1907.0.17833\bin\Firefox_Extension\{442718d9-475e-452a-b3e1-fb1ee16b8e9f}\components;C:\Users\Fabio\AppData\Roaming\Dashlane\6.1907.0.17833\ucrt;C:\Users\Fabio\AppData\Roaming\Dashlane\6.1907.0.17833\bin\Qt;C:\Users\Fabio\AppData\Roaming\Dashlane\6.1907.0.17833\bin\Ssl
DriverData=C:\Windows\System32\Drivers\DriverData
HOMEDRIVE=C:
HOMEPATH=\Users\Fabio
LDRAWDIR=C:\Users\Public\Documents\LDraw
LOCALAPPDATA=C:\Users\Fabio\AppData\Local
LOGONSERVER=\\LAPTOP-5NFKIEGS
MOZ_PLUGIN_PATH=C:\PROGRAM FILES (X86)\FOXIT SOFTWARE\FOXIT READER\plugins\
NUMBER_OF_PROCESSORS=4
OneDrive=C:\Users\Fabio\OneDrive
OneDriveConsumer=C:\Users\Fabio\OneDrive
OS=Windows_NT
Path=C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files\scicoslab-4.4.2\bin;C:\Program Files (x86)\PC Connectivity Solution\;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\MATLAB\R2017b\bin;C:\Program Files (x86)\QuickTime\QTSystem\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files (x86)\nodejs\;C:\Program Files\Microsoft Windows Performance Toolkit\;C:\Program Files\CMake\bin\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Program Files (x86)\dotnet\;C:\Program Files (x86)\STMicroelectronics\STM32 ST-LINK Utility\ST-LINK Utility;C:\Program Files\PuTTY\;C:\Users\Fabio\AppData\Local\Programs\Python\Python38-32;C:\Users\Fabio\AppData\Local\Programs\Python\Python38-32\Scripts\;C:\Users\Fabio\Documents\SWIG\swigwin-4.0.2;C:\Program Files (x86)\GnuWin32\bin;C:\Program Files (x86)\Nordic Semiconductor\nrf-command-line-tools\bin\;C:\ProgramData\chocolatey\bin;C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.27.29110\bin\Hostx86\x86;C:\Program Files\Git\cmd;C:\src\vcpkg;C:\Program Files (x86)\GNU Arm Embedded Toolchain\9 2020-q2-update\bin;C:\Users\Fabio\AppData\Local\Programs\Python\Python38-32\Scripts\;C:\Users\Fabio\AppData\Local\Programs\Python\Python38-32\;C:\Users\Fabio\AppData\Local\Microsoft\WindowsApps;C:\Users\Fabio\AppData\Roaming\Dashlane\4.6.6.23032\bin\Firefox_Extension\{442718d9-475e-452a-b3e1-fb1ee16b8e9f}\components;C:\Users\Fabio\AppData\Roaming\npm;C:\Program Files (x86)\Atmel\Flip 3.4.7\bin;C:\Users\Fabio\AppData\Local\Programs\Python\Python38-32;C:\Users\Fabio\AppData\Local\Programs\Microsoft VS Code Insiders\bin
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PY;.PYW
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 78 Stepping 3, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=4e03
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PROMPT=$P$G
PSModulePath=C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\;C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules
PUBLIC=C:\Users\Public
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\Users\Fabio\AppData\Local\Temp
TMP=C:\Users\Fabio\AppData\Local\Temp
USERDOMAIN=LAPTOP-5NFKIEGS
USERDOMAIN_ROAMINGPROFILE=LAPTOP-5NFKIEGS
USERNAME=Fabio
USERPROFILE=C:\Users\Fabio
VS140COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\
VSSDK140Install=C:\Program Files (x86)\Microsoft Visual Studio 14.0\VSSDK\
windir=C:\WINDOWS

Hope this can help.

Thank you!

Fabio

[Karl Ylvisaker]

Hello Fabio,

Sorry for my late reply.
Did you succeed in getting the pc-ble-driver-py to work as expected?
I have tried to replicate your issue with the pc-ble-driver compilation on my end by following your detailed explanation, but unfortunately I am not encountering the same errors as you.

Could you run this command in a regular command prompt (not PowerShell):

"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" -format Json

And post the output here?

Looking forward to resolving this issue together!

Best regards,
Karl

[Fabio Ballanti]

Hello Karl,

Thank you for your reply, don't worry if it took so long.

Karl Ylvisaker said:

Did you succeed in getting the pc-ble-driver-py to work as expected?

No, I didn't yet... when have a free spot I will go for it... in the meanwhile I've imported the pc-ble-driver-py library on my scripts and started working on advertising on BLE, and found other troubles 

Karl Ylvisaker said:

Could you run this command in a regular command prompt (not PowerShell):

OK, here is the output:

C:\WINDOWS\system32>"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" -format Json
[
  {
    "instanceId": "30540051",
    "installDate": "2017-12-08T21:04:45Z",
    "installationName": "VisualStudio/15.9.29+28307.1300",
    "installationPath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Community",
    "installationVersion": "15.9.28307.1300",
    "productId": "Microsoft.VisualStudio.Product.Community",
    "productPath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Community\\Common7\\IDE\\devenv.exe",
    "state": 4294967295,
    "isComplete": true,
    "isLaunchable": true,
    "isPrerelease": false,
    "isRebootRequired": false,
    "displayName": "Visual Studio Community 2017",
    "description": "Free, fully-featured IDE for students, open-source and individual developers",
    "channelId": "VisualStudio.15.Release",
    "channelPath": "C:\\Users\\Fabio\\AppData\\Local\\Microsoft\\VisualStudio\\Packages\\_Channels\\4CB340F5\\catalog.json",
    "channelUri": "https://aka.ms/vs/15/release/channel",
    "enginePath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\Installer\\resources\\app\\ServiceHub\\Services\\Microsoft.VisualStudio.Setup.Service",
    "releaseNotes": "https://go.microsoft.com/fwlink/?LinkId=660692#15.9.29",
    "thirdPartyNotices": "https://go.microsoft.com/fwlink/?LinkId=660708",
    "updateDate": "2020-11-12T05:37:03.7464676Z",
    "catalog": {
      "buildBranch": "d15.9",
      "buildVersion": "15.9.28307.1300",
      "id": "VisualStudio/15.9.29+28307.1300",
      "localBuild": "build-lab",
      "manifestName": "VisualStudio",
      "manifestType": "installer",
      "productDisplayVersion": "15.9.29",
      "productLine": "Dev15",
      "productLineVersion": "2017",
      "productMilestone": "RTW",
      "productMilestoneIsPreRelease": "False",
      "productName": "Visual Studio",
      "productPatchVersion": "29",
      "productPreReleaseMilestoneSuffix": "1.0",
      "productRelease": "RTW",
      "productSemanticVersion": "15.9.29+28307.1300",
      "requiredEngineVersion": "1.18.1063.29791"
    },
    "properties": {
      "campaignId": "711569342.1512751140",
      "canceled": "0",
      "channelManifestId": "VisualStudio.15.Release/15.9.29+28307.1300",
      "nickname": "",
      "setupEngineFilePath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\Installer\\vs_installershell.exe"
    }
  },
  {
    "instanceId": "ba2d467e",
    "installDate": "2019-12-17T19:22:43Z",
    "installationName": "VisualStudio/16.8.1+30711.63",
    "installationPath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community",
    "installationVersion": "16.8.30711.63",
    "productId": "Microsoft.VisualStudio.Product.Community",
    "productPath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\Common7\\IDE\\devenv.exe",
    "state": 4294967295,
    "isComplete": true,
    "isLaunchable": true,
    "isPrerelease": false,
    "isRebootRequired": false,
    "displayName": "Visual Studio Community 2019",
    "description": "Powerful IDE, free for students, open-source contributors, and individuals",
    "channelId": "VisualStudio.16.Release",
    "channelUri": "https://aka.ms/vs/16/release/channel",
    "enginePath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\Installer\\resources\\app\\ServiceHub\\Services\\Microsoft.VisualStudio.Setup.Service",
    "releaseNotes": "https://go.microsoft.com/fwlink/?LinkId=660893#16.8.1",
    "thirdPartyNotices": "https://go.microsoft.com/fwlink/?LinkId=660909",
    "updateDate": "2020-11-14T03:31:53.1405875Z",
    "catalog": {
      "buildBranch": "d16.8",
      "buildVersion": "16.8.30711.63",
      "id": "VisualStudio/16.8.1+30711.63",
      "localBuild": "build-lab",
      "manifestName": "VisualStudio",
      "manifestType": "installer",
      "productDisplayVersion": "16.8.1",
      "productLine": "Dev16",
      "productLineVersion": "2019",
      "productMilestone": "RTW",
      "productMilestoneIsPreRelease": "False",
      "productName": "Visual Studio",
      "productPatchVersion": "1",
      "productPreReleaseMilestoneSuffix": "1.0",
      "productSemanticVersion": "16.8.1+30711.63",
      "requiredEngineVersion": "2.8.3267.30329"
    },
    "properties": {
      "campaignId": "1420090839.1575124163",
      "channelManifestId": "VisualStudio.16.Release/16.8.1+30711.63",
      "nickname": "",
      "setupEngineFilePath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\Installer\\vs_installershell.exe"
    }
  }
]

Thanx,

Fabio

[Karl Ylvisaker]

Fabio Ballanti said:

Thank you for your reply, don't worry if it took so long.

Thank you for your patience and understanding.

Fabio Ballanti said:

No, I didn't yet... when have a free spot I will go for it... in the meanwhile I've imported the pc-ble-driver-py library on my scripts and started working on advertising on BLE, and found other troubles

I am sorry to hear that! But, at least the installation of the driver ( pip install pc-ble-driver-py ) was successful this time, correct? So we'll primarily have to resolve issues with using the driver directly. Please do not hesitate to open a separate ticket for any pc-ble-driver-py issues you might have ( such as the one we are discussing in the other ticket currently ).

Fabio Ballanti said:

OK, here is the output:

Thank you. Everything looks as it should here. Could you run the vs_installer.exe file from \Microsoft Visual Studio\Installer, click modify, and make sure you have the "english" language pack installed? This might seem trivial and unrelated, but I have heard of instances in which this has proven to be a cause of errors.

Best regards,
Karl