All,
Just updated my laptop from openSUSE Leap 15.4 to Tumbleweed. I also use picoprobe/openocd and another pico to quickly and easily flash to the pico from the command line. Since I had done a fresh install, I was rebuilding all tools from scratch. I was absolutely shocked at the 1.4 Gigabytes of information pulled in with picoprobe by git submodule update --init. This did not happen when I last built picoprobe. Further, this also downloaded a new copy of freeRTOS - despite already having it in /opt and having FREERTOS_KERNEL_PATH set in the environment.
When we last built picoprobe on 9/12/2022, there was a simple single src directory and it happily used the existing freeRTOS repository. The entire repository was less than 100K and there were no insanely large submodules.
Now when I run submodule init, it literally takes 1.4G+ of downloaded .git information including over 400M+ for the CMSIS_5 (including and the CMSIS_5 Documentation).
Is this really necessary? The original picoprobe.uf2 was fine. Now the name has changed to debugprobe.uf2 and it takes gigabytes of downloads to build to do the same thing. Is there a way to avoid this additional bloat?
What changed?
Just updated my laptop from openSUSE Leap 15.4 to Tumbleweed. I also use picoprobe/openocd and another pico to quickly and easily flash to the pico from the command line. Since I had done a fresh install, I was rebuilding all tools from scratch. I was absolutely shocked at the 1.4 Gigabytes of information pulled in with picoprobe by git submodule update --init. This did not happen when I last built picoprobe. Further, this also downloaded a new copy of freeRTOS - despite already having it in /opt and having FREERTOS_KERNEL_PATH set in the environment.
When we last built picoprobe on 9/12/2022, there was a simple single src directory and it happily used the existing freeRTOS repository. The entire repository was less than 100K and there were no insanely large submodules.
Now when I run submodule init, it literally takes 1.4G+ of downloaded .git information including over 400M+ for the CMSIS_5 (including and the CMSIS_5 Documentation).
Is this really necessary? The original picoprobe.uf2 was fine. Now the name has changed to debugprobe.uf2 and it takes gigabytes of downloads to build to do the same thing. Is there a way to avoid this additional bloat?
What changed?
Statistics: Posted by drankinatty — Sat Jul 13, 2024 6:27 am — Replies 0 — Views 96