Closed zxkmm closed 2 months ago
Doh, sry totally forgot about this :/
This is nice to be able to tell about any binary what exact version it was built with :)
To fix the detection issue in cmake however it is potentially enough to replace "arm-none-eabi-g++ -v" with "${CMAKE_CXX_COMPILER} -v" (havent tested this yet :))
Will send that as a separate PR, this I'll try to read in the evening it should go in regardless 👍
Hi , I think that @NotherNgineer , already merged another PR that writes in the user settings the used gcc version to create that binary . Is that the same issue 🤔?
Hi , I think that @NotherNgineer , already merged another PR that writes in the user settings the used gcc version to create that binary . Is that the same issue 🤔?
No. It’s somehow not accurate.
It would be better if there was a single message versus one per ELF file -- because now the percentage ROM utilization scrolls off the screen.
It would be better if there was a single message versus one per ELF file -- because now the percentage ROM utilization scrolls off the screen.
Thanks! I'll submit with a new PR with compare.
After thinking, I think it's not quite make sense to compress the output, since it could be possible if ccache
mistakenly skipped compiling in some edge case that we didn't know, and it's would be harder to debug.
and about flushing the screen, I think other things do that as well, for example cmake itself:
[ 64%] Built target baseband_gps_sim.elf
[ 66%] Built target baseband_test.elf
[ 70%] Built target baseband_audio_beep.elf
[ 70%] Built target baseband_spectrum_painter.elf
[ 73%] Built target hackrf_usb_objects
[ 77%] Built target hackrf_usb_ram_objects
[ 80%] Built target hackrf_usb_dfu_objects
[ 97%] Built target application.elf
[ 97%] Built target hackrf_usb.elf
[ 97%] Built target hackrf_usb_ram.elf
[ 97%] Built target hackrf_usb_dfu.elf
[ 97%] Built target application
[ 97%] Built target hackrf_usb_ram.bin
[ 97%] Built target hackrf_usb.bin
[ 97%] Built target hackrf_usb_dfu.bin
[100%] Built target baseband
SO i added a new PR just simply tuned the print order. This we can see the % in last screen.
it's because it happend on me and gull that the current check gcc ver isn't that reliable. This is read from elf target which were compiled, which should be accurate
NOTE that i'm not sure if this will break pipeline. i need to check on my fork HOWEVEReven after it passed from my side it's still need a nightly release to check workreadelf cmd is from binutils.
which idk if it's included in pipeline.(edit: pipeline compile passed)https://github.com/zxkmm/mayhem-firmware/actions/runs/8778357213