Error building 'boringssl' on linux about lightning-app HOT 5 CLOSED

For now, an easy way to bypass this until there's a more general solution, is to add -Wno-implicit-fallthrough to cflags field in target-defaults in apps/desktop/node_modules/grpc/binding.gyp file, which is pulled in with npm run setup.

Update: see grpc/grpc#12536 for more details.

from lightning-app.

Even the latest release of grpc (1.6.6) uses an ancient version of boringssl that's over a thousand commits behind. Naïvely updating to the latest version has even worse errors =[

from lightning-app.

It seems that the problem is in grpc v1.1.1, which depends on an older boringssl version, which doesn't have marks for switch-statement fallthrough behaviour. It could be fixed on the grpc side by updating git submodule for boringssl.

from lightning-app.

Thanks @mrwhythat. I'll play around with this a bit. Building boringssl on Windows was a huge pain as well, and if this works, that would be a big plus.

from lightning-app.

This would most likely get fixed if the following is done:

1. https://boringssl.googlesource.com/boringssl/+/60931e2d8afff685f5460cf9a88469b96942849b (merged)
2. Submodule update PR (that contains above fix): grpc/grpc#12922 (PR contributor seems to have bit of an issue here I think)
3. Bump grpc npm package to get the fixes.

from lightning-app.