Many, many files have Windows line-endings, for example the `./build_all.sh` bash script in micro-ecc, but many files more as well.
#!/bin/bash^M^M# This script will use git (must be in $PATH) and arm-none-eabi tools in combination with GNU Make^M# to both fetch and compile all variants of micro-ecc for the nRF5 families^M^Mif ! [ -x "$(command -v git)" ]; then^M echo 'git is not installed. Please install and append to PATH.' >&2^M exit^Mfi^M^Mif [ ! -f micro-ecc/uECC.c ]; then^M echo "micro-ecc not found! Let's pull it from HEAD."^M git clone github.com/.../micro-ecc.git^Mfi^M^Mmake -C nrf51_armgcc/armgcc &&^Mmake -C nrf51_iar/armgcc &&^Mmake -C nrf51_keil/armgcc &&^Mmake -C nrf52hf_armgcc/armgcc &&^Mmake -C nrf52hf_iar/armgcc &&^Mmake -C nrf52hf_keil/armgcc &&^Mmake -C nrf52nf_armgcc/armgcc &&^Mmake -C nrf52nf_iar/armgcc &&^Mmake -C nrf52nf_keil/armgcc^M
This leads to faults in Linux/Unix machines:
./build_all.sh: bad interpreter: /bin/bash^M: no such file or directory
The executable bit is not set either.
Please, consider removing Ctrl+M characters before submitting the code to your internal repository. In that way it's the least likely it ends up in your zip files.
Thank you for the report, this has been reported previously in this thread as well. I have notified the developers about your report.
Yes, please, also indicate the number of files it is about.
grep -r -l --binary -P '\x0d' . | wc -l
returns 11810 hits.
Note, also that it was reported for SDK 14, while I'm at SDK 15.3.0. Perhaps also include in your release build script for the corresponding zip files a series of tests / bug regression tools. It's better to automate these things. That saves up valuable space in our heads to do true contributions. :-)