Unable to build nRF51 Bluetooth Driver 0.5.0

RE: Unable to build nRF51 Bluetooth Driver 0.5.0

Bjørn Inge — Wed, 27 Jan 2016 21:30:00 GMT

Thanks for sharing your findings.

RE: Unable to build nRF51 Bluetooth Driver 0.5.0

jpo38 — Wed, 27 Jan 2016 14:57:26 GMT

I finally got it compile and work. If one needs to do that, here are the steps to follow:

1- Get driver sources from github.com/.../v0.5.0

2- Download and install all dependencies as requested by README.md, except for MinGW (proposed version does not support x64)

3- Get w64 MinGW installer and install the version coresponding to the one referenced by README.md: 4.8.2, thread posix

4- Build boost as documented (README.md), but with additional b2 parameter: address-model=64

5- From driver's script folder, replace i386 by X64 in msvc_def_to_lib.bat.in file (else, you'll get a x64 .dll but a x86 .lib....)

6- Run build.py command (as documented by README.md) once (to have SDK be downloaded), it will fail with error error: expected primary-expression before 'volatile' #define __I volatile. This is because Nordic's __I variable conflicts with a MinGW 64bits variable.

7- Go to the SDK folder and replace all __I by __NRF_I to resolve the conflict (there should be 251 instances in components\toolchain\gcc\core_cm0.h and components\device\nrf51.h)

8- Run build.py script again. .dll and .lib will be generated for x64 target!

RE: Unable to build nRF51 Bluetooth Driver 0.5.0

jpo38 — Wed, 27 Jan 2016 14:41:56 GMT

Hi, I tested win32, and it compiles OK. I finally succeeded, I post details below as an answer. You may check it to extend your build scripts to support x64 (there's only a few changes I had to do, but you can't build without them).

RE: Unable to build nRF51 Bluetooth Driver 0.5.0

Bjørn Inge — Wed, 27 Jan 2016 08:22:25 GMT

It does build 64 bit on linux and osx so it should be possible to accomplish. That said it might be that the build script or patched SDK header files etc. fail to take the mingw gcc 64 bit compiler into consideration as it hasn't been tested. To rule out other problems, could you try to build 32 bit as documented first, if you haven't already done so?