Agreed, we need to document this more. And I’ll add a win32 extension example as well.
For your use case, you should use the “.lib” extension for libraries on windows. And you don’t need to add any libs flags to add your own provided lib (we do that for you).
As for the C++ implementation, you shouldn’t need to link in the C++ dll’s either.
If you do need to add a library from visual studio, you would write their file name like so:
x86_64-win32:
context:
libs: ["Ws2_32.lib"]
There (a little) more information here regarding how to remove debug functionality from the engine. Notice that we specify the windows libraries by their full filename.