Building the examples in pc-ble-driver from scratch

RE: Building the examples in pc-ble-driver from scratch

brianreinhold — Sun, 13 Oct 2019 11:34:53 GMT

Turns out that it was because you used a cpp (C++) file and the example is in C. Changing the the cpp to c in the file created by the VS Console app solves the problem - for anyone else who stumbles on the same problem. (One of those things you don't think about when using the VS shell project creators).

There is another issue that caused my library problems. Even though its a static library I linked to, if I set the project properties CodeGeneration settings to use static linking, the project will not build. I get all kinds of warning conflicts about already imported libraries by the Nordic static library which eventually become warnings. So the only way to build the project is to set the code generation to dynamic (dll) linking.

Needless to say, I do not understand why that is so.

But if I do, I can use the property pages to point to the Nordic static library instead of bringing it into my source or lib 'filter' folder in my project.

RE: Building the examples in pc-ble-driver from scratch

brianreinhold — Thu, 10 Oct 2019 23:52:15 GMT

I can't attach files here so I will send it to you in an email

RE: Building the examples in pc-ble-driver from scratch

Masahiro Kondo — Thu, 10 Oct 2019 21:57:27 GMT

I checked library just in case but it is definitely nrf-ble-driver-sd_api_v6-mt-static-4_1_1.lib in source files but somehow it doesn't seem to find sd_ functions. If you could upload project/sln files, that will be much appreciated. It must be some simple setting somewhere I don't understand..

RE: Building the examples in pc-ble-driver from scratch

brianreinhold — Thu, 10 Oct 2019 08:05:12 GMT

Hopefully whats in your library 'lib' is the static lib, not the dynamic. The error indictes VS is not finding your static library. If helpful, I can zip up my entire VS project/sln for you. I have started the attempt to make it secure (force pairing) which does not work yet. It is easy to remove that code since I have not gotten very far. I get another error that makes no sense but I have gotten the central to initiate pairing!

RE: Building the examples in pc-ble-driver from scratch

Masahiro Kondo — Wed, 09 Oct 2019 23:28:11 GMT

Hi, I followed Sigurd's instruction with Console app, but I get lots of errors which are very similar to brianreinhold had before (e.g. unresolved external symbol _sd_ble_gap_conn_param_update referenced...). I did add .lib to Source Files instead of linker settings. Is there any instruction missing? I can see nrf-ble-driver-sd_api_v6-mt-4_1_1.dll, do I need to do anything about this? I am using VisualStudio 2019.

RE: Building the examples in pc-ble-driver from scratch

brianreinhold — Mon, 07 Oct 2019 08:34:23 GMT

So far that is what I have done. Except I did not start with the Console project; I started with an empty project but all my properties are filled in as above. I used the properties pages to point to the library but did not add it to the source files. Did that; made no difference. Same 10 LNK2019 errors. Out of desperation I will blow away everything, start from scratch from a console app instead of an empty project and see if that works. (I also have _WIN32 which I think it should be given what's in the source code.)

It makes no sense, There must be some other piece of configuration information that I have not gotten. I have the configuration set to x64 and not x86 (I think I tried that out of desperation too). Is that a potential issue?

I blew away everything and started with a console app instead of an empty project. That worked. I cannot tell the difference but in the console app I did not use the property pages to point to the static library. I added it to the source file filter (did that in the empty project too but it did not help). The only difference between the two is the linking of the libraries. In the empty project I set the build to use static debug and set the linker to point to the libraries (this is what I have always done in Visual Studio). Any idea why that does not work? I might want to make this a Win32 GUI application and now I am afraid as how to link needed libraries. Is it something special about the nordic library that CANT be linked via the properties pages?

I verified the answer (though I don't know why I cant sue the property pages). But in doing so the issue got closed. So I had to reject the answer. That I will change if someone can give any insight into why the library has to be linked this way ...

RE: Building the examples in pc-ble-driver from scratch

Sigurd — Mon, 07 Oct 2019 07:57:16 GMT

Hi,

Here are the steps I used to compile the project with VS Studio 2017:

New project -> Visual C++ -> Windows Console Application -> OK
In ConesoleApplication.cpp, I replaced the content with this one -> https://github.com/NordicSemiconductor/pc-ble-driver/blob/master/examples/heart_rate_collector/main.c
In the Solution Explorer, right click on ConsoleApplication -> Properties -> VC++ Directories -> “Include Directories” -> Edit -> New line, find the pc-ble-driver include folder , (e.g. C:\Nordic\nrf-ble-driver-4.1.1-win_x86_32 \include\sd_api_v6) -> OK.
In the Solution Explorer, right click on ConsoleApplication -> Properties -> C/C++ -> Preprocessor -> Preprocessor Definitions -> Edit-> By default there are “WIN32, _DEBUG and _CONSOLE. Add:

PC_BLE_DRIVER_STATIC

_CRT_SECURE_NO_WARNINGS

NRF_SD_BLE_API=6
In the Solution Explorer, right click on ConsoleApplication -> Properties -> C/C++ -> Precompiled Headers -> Precompiled Header -> Set to “Not using precompiled Headers”.
In the Solution Explorer, right click on Header Files -> Add -> Existing Item.. -> Mark all the .h files in folder “nrf-ble-driver-4.1.1-win_x86_32\include\sd_api_v6”, there should be 18 files -> OK.
In the Solution Explorer, right click on “Source Files”, Add -> Existing Item.. -> Find the lib folder, and add nrf-ble-driver-sd_api_v6-mt-static-4_1_1.lib -> OK
Build -> Build Solution

RE: Building the examples in pc-ble-driver from scratch

brianreinhold — Fri, 04 Oct 2019 16:48:58 GMT

Interesting. Visual Studio already has a parameter setting to indicate whether one is using static or dynamic libraries.

In any case, adding those two reduces the number of undefined symbols from 16 to 9. There must be more preprocessors or libraries missing.

1>nrf-ble-driver-sd_api_v6-mt-static-4_1_1.lib(sd_rpc_impl.cpp.obj) : error LNK2019: unresolved external symbol __imp_strncpy referenced in function sd_rpc_serial_port_enum
1>nrf-ble-driver-sd_api_v6-mt-static-4_1_1.lib(serial_port_enum.cpp.obj) : error LNK2019: unresolved external symbol __imp_strstr referenced in function "class std::list<struct SerialPortDesc,class std::allocator<struct SerialPortDesc> > __cdecl EnumSerialPorts(void)" (?EnumSerialPorts@@YA?AV?$list@USerialPortDesc@@V?$allocator@USerialPortDesc@@@std@@@std@@XZ)
1>nrf-ble-driver-sd_api_v6-mt-static-4_1_1.lib(serial_port_enum.cpp.obj) : error LNK2019: unresolved external symbol __imp_strtok_s referenced in function "class std::list<struct SerialPortDesc,class std::allocator<struct SerialPortDesc> > __cdecl EnumSerialPorts(void)" (?EnumSerialPorts@@YA?AV?$list@USerialPortDesc@@V?$allocator@USerialPortDesc@@@std@@@std@@XZ)
1>nrf-ble-driver-sd_api_v6-mt-static-4_1_1.lib(serial_port_enum.cpp.obj) : error LNK2019: unresolved external symbol __imp__stricmp referenced in function "class std::list<struct SerialPortDesc,class std::allocator<struct SerialPortDesc> > __cdecl EnumSerialPorts(void)" (?EnumSerialPorts@@YA?AV?$list@USerialPortDesc@@V?$allocator@USerialPortDesc@@@std@@@std@@XZ)
1>nrf-ble-driver-sd_api_v6-mt-static-4_1_1.lib(disphelper.c.obj) : error LNK2019: unresolved external symbol __imp__gmtime64 referenced in function ConvertTimeTToVariantTime
1>nrf-ble-driver-sd_api_v6-mt-static-4_1_1.lib(disphelper.c.obj) : error LNK2019: unresolved external symbol __imp__localtime64 referenced in function ConvertTimeTToVariantTime
1>nrf-ble-driver-sd_api_v6-mt-static-4_1_1.lib(disphelper.c.obj) : error LNK2019: unresolved external symbol __imp__mktime64 referenced in function ConvertTimeTToVariantTime
1>nrf-ble-driver-sd_api_v6-mt-static-4_1_1.lib(jlinkid_reg_lookup.cpp.obj) : error LNK2019: unresolved external symbol __imp_memchr referenced in function "char const * __cdecl std::_Find_unchecked1<char const *,unsigned char>(char const *,char const *,unsigned char const &,struct std::integral_constant<bool,1>)" (??$_Find_unchecked1@PEBDE@std@@YAPEBDPEBD0AEBEU?$integral_constant@_N$00@0@@Z)
1>nrf-ble-driver-sd_api_v6-mt-static-4_1_1.lib(jlinkid_reg_lookup.cpp.obj) : error LNK2019: unresolved external symbol __imp_realloc referenced in function "public: void __cdecl std::_Buf<char>::_Insert<char const *>(char const *,char const *)" (??$_Insert@PEBD@?$_Buf@D@std@@QEAAXPEBD0@Z)

RE: Building the examples in pc-ble-driver from scratch

Sigurd — Fri, 04 Oct 2019 14:13:48 GMT

Hi,

[quote user=""]There were several definitions that were not understood. Turns out I have to define the preprocessor variable to set the version as follows #define NRF_SD_BLE_API 6. [/quote]

You also need to add PC_BLE_DRIVER_STATIC and _CRT_SECURE_NO_WARNINGS