-
Notifications
You must be signed in to change notification settings - Fork 193
Remove static_library for arm architectures to build keytar.node also… #92
Conversation
This comment has been minimized.
This comment has been minimized.
Hi, can we get this reviewed? We are also running into the same problem on the pi. |
This pull fix ARM build hope you merge it soon :) |
@tzarebczan @surferandi @kodxana it's not clear to me how this fixes the underlying issue. #79 had a decent writeup about the issue they were seeing with linking to shared libraries, and I'd love similar context for this change because I don't have access to ARM hardware myself. Are you able to provide the |
@shiftkey ['target_arch=="arm"', { 'type': 'static_library' }] |
@kodxana so this should be cc @SteveDesmond-ca would love your input on this |
@shiftkey target_arch=="armhf" this is architecture used by most of the Pi |
My suggestion would be to change the ARM processors basically come in 3 flavors days: Raspbian (the de-facto Raspberry Pi flavor of Linux) is 32-bit only last I checked. While other distros exist that target 64-bit hardware, they're definitely not the majority. On the Chromebook side of things, it's currently about a 50/50 split between 32- and 64-bit CPUs, for those that use ARM. Pretty much all new smartphone hardware being made today is 64-bit, but there's still a lot of 32-bit out there. |
Apologies for the delay in getting back to this. This has been really hard for me to test due to lack of insight into the ARM ecosystem and what we should be doing here, but I'm going to take this in and see if it makes these use cases better. |
This change is available in version |
… on raspberry pi, see #91