-
Sun 2021.10.31
'It is however possible that at some point you followed some steps you found on the forum or googled that would have permanently installed the compiler.'
Thanks @Gordon, that worked.
Had I not taken extensive notes during this recent VSCode revitalization, it is unlikely I would have discoverd how gcc gets installed.
The day I re-cloned the Espruino repository, I upgraded nRFConnect which forced the install of the SDK15 for the nRF52 chips, and also upgraded make, nrfutil, and esptool to get the latest versions.
During the process of upgrading the above, (maybe during some future install - which one)
this warning popped up:
'The program 'arm-none-eabi-gdb' is currently not installed. You can install it by typing:
sudo apt install gdb-arm-none-eabi'I followed the instructions:
sudo apt install gdb-arm-none-eabi
which unpacks and installs (around thirty lines in)
Get:2 http://archive.ubuntu.com/ubuntu xenial/universe amd64 gcc-arm-none-eabi amd64 15:4.9.3+svn231177-1 [17.3 MB]
8% [2 gcc-arm-none-eabi 1,871 kB/17.3 MB 11%]
So, future firmware builders, beware when upgrading nRFConnect to build for nRF52
You are reading a single comment by @Robin and its replies.
Click here to read the full conversation.
Robin
Yes, that's entirely possible. While I try and document what's needed in https://github.com/espruino/Espruino/blob/master/README_Building.md I can't document every eventuality - specifically that something has been set up on the computer beforehand that wouldn't normally be set up.
The provision script does not permanently install GCC - it does it only for that session - so this exact thing does not happen. It is however possible that at some point you followed some steps you found on the forum or googled that would have permanently installed the compiler.
I can't remember the specific version used but it's easy enough to find in
scripts/provision.sh