Install patches in provision ? #6293
Replies: 1 comment
-
Posted at 2020-07-01 by @gfwilliams You're asking why the SDK files aren't in GitHub? I just got fed up with the amount of SDK files that were in GitHub - especially for Nordic where every SDK has its own set. It was also hard to keep track of what had been changed in the SDK, which makes it more painful to upgrade SDK versions. ESP8266/32 install the SDK files in provision too, and I thought I'd take some of their ideas for SDK15 :) Posted at 2020-07-01 by JumJum Hmm, good answer ;-) Posted at 2020-07-03 by @gfwilliams I feel like moving the folders is going to be too much work - IIRC there's an awful lot hard-coded in the Makefile. Is there a reason you couldn't just have a whole different copy of the Espruino repository for edge/release/etc? It can't add that much extra disk space... Posted at 2020-07-03 by JumJum Sounds like an OGP (old guys problem), that I would like to get rid off. Posted at 2020-07-04 by @allObjects @jumjum, Could Symbolic Links help with that 'synchronization'? If it is on directory level, that could work... if it is on some individual files in a directory but not on others, then it is not such a good idea... Posted at 2020-07-06 by JumJum Hmm, I will check. Thanks for this hint |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Posted at 2020-07-01 by JumJum
targetlibs holds a lot of nrf relevant files.
patches to these files (based on $PROVISION_NRF_SDK15) are installed in provision.sh
Is there a special reason why these changes are not directly in targetlibs ?
Is there a reason, not to install on default ?
Beta Was this translation helpful? Give feedback.
All reactions