build pc-ble-driver static library in Visual Studio

[brianreinhold]

Has anyone successfully built the pc-ble-driver static library in Visual Studio as a project? In this manner one could debug applications that use the library when there are problems in the library by stepping into the library source code. Right now one has to install several third party programs like Cmake, ninja, vcpkg and who knows what else to build the static library and that does not help debugging issues. It looks like one needs several third party libraries as well

asio,

catch2,

and spdlog.  What are these? The last looks like a logging system but the first two I have never heard of.

Maybe all I need is the asio third party library if not doing unit tests? I don't see any spdlog references in the driver source code or header files...

Looking at that I see an asio without boost and an asio with boost. I see boost in the name of some header files but the documentation states to fetch just asio 'vcpkg -install asio' which suggests asio without boost. I would like to minimize the downloads!

[Einar Thorsrud]

Hi,

What are these?

You do not typically need to care about the dependencies other than making sure they are met, but if you want to know more about them I guess it is better to check their repositories and/or documentation:

• https://github.com/chriskohlhoff/asio
• https://github.com/catchorg/Catch2
• https://github.com/gabime/spdlog

Unless you have a lot of time and want to tweek things to your liking, I suggest you just follow the instructions under Compiling pc-ble-driver from source when you need to build the pc-ble-driver yourself.

[brianreinhold]

I already know that I do not need Catch2 and spdlog..With asio is it not clear if it is the boost or non boost version

[Einar Thorsrud]

Hi,

You do not need boost for building the pc-ble-driver 4.0.0 (it was needed for version 3, but that did not use asio).

[brianreinhold]

The idea is also to be able to step through the driver code to solve problems like I am getting with a reply method in the security exchange. I was asked to do that in another post by a Nordic engineer. It was something I was hoping to avoid given all the third party software I would have to install on my system.