BOBAH

just for information / state of progress https://sourceforge.net/p/sdcc/bugs/3303/#13df

https://sourceforge.net/p/sdcc/bugs/3303/#6824 remove dead functions at link time Yes! I did it! But for STM8 and as proof of concept The results are the following, where "original" SDCC is 4.1.0 #12072 (MINGW64): "Hello word!" from the box: - original 667 bytes - my 529 bytes Stripping results: 1. LOAD GPIO_Init - 218 bytes 2. LOAD GPIO_WriteReverse - 9 bytes 3. LOAD ___str_0 - 105 bytes 4. LOAD Delay - 4 bytes 5. LOAD main - 26 bytes 6. LOAD assert_failed - 7 bytes 7. LOAD TRAP_IRQHandler - 1 bytes...

It took a long time, but I managed to overcome all obstacles :) First of all, I was able to compile full set of files SDCC under Windows using Cygwin with latest cygwin-gcc, Boost, C-headers and C-libs And I able to debug all executable files as well as use cool IDE - VScode for developments Unfortunately I am forced to use Cygwin build for target instead of MinGW, because some of builds requires wait function for execution of sub processes, which is not supported by mingw The installation of Cygwin...

It took a long time, but I managed to overcome all obstacles :) First of all, I was able to compile full set of files SDCC under Windows using Cygwin with latest cygwin-gcc, Boost, C-headers and C-libs And I able to debug all executable files as well as use cool IDE - VScode for developments Unfortunately I am forced to use Cygwin build for target instead of MinGW, because some of builds requires wait function for execution of sub processes, which is not supported by mingw The installation of Cygwin...

It took a long time, but I managed to overcome all obstacles :) First of all, I was able to compile full set of files SDCC under Windows using Cygwin with latest cygwin-gcc, Boost, C-headers and C-libs And I able to debug all executable files as well as use cool IDE - VScode for developments Unfortunately I am forced to use Cygwin build for target instead of MinGW, because some of builds requires wait function for execution of sub processes, which is not supported by mingw The installation of Cygwin...

It took a long time, but I managed to overcome all obstacles :) First of all, I was able to compile full set of files SDCC under Windows using Cygwin with latest cygwin-gcc, Boost, C-headers and C-libs And I able to debug all executable files as well as use cool IDE - VScode for developments Unfortunately I am forced to use Cygwin build for target instead of MinGW, because some of builds requires wait function for execution of sub processes, which is not supported by mingw The installation of Cygwin...

Thanks all for responses, @roybaer, this project is used not only under Linux, but also in other OSs that can start Platformio and / or VSCode + Platformio-plugin as well as Arduino. If you look from this point of view, then this project has chances to be in demand in wide circles (and not only in the context of STM8, which surpasses AVR in characteristics and price, and at the same time is as close to electrical characteristics as possible). But there is one drawback: SDCC is pure-C, while Arduino-like...

I spent 3 days, but I could not prepare at least some working environment for the build binaries for Windows. - the VS solution/projects is old and don't build full staff of executable files - Cygwin under Windows build all executable, but they provide wrong application path (always say /usr/bin/) and cannot find other files (executable and headers+libs), so build always left with "file not found" error - platform-specific code refers to _WIN32 (and WIN32) defines that related to VS but not Cygwin...