John Brandwood

Yes, certainly from my point of view.

The config.h is only needed for a seperate compilation that doesn't use SDCC's ".configure", such as when using Visual Studio and msbuild. If you're trying to build on linux or MacOS, or Windows with MSYS2, then you just need a simple build script to use SDCC's ".configure", with settings to tell it to look for include files in the sdcc/include directory. Here's one for a minimal SDCC build. You can play with the configuration options and see where/if/when it breaks. As for sdar, sdld, etc ... I...

The config.h is only needed for a seperate compilation that doesn't use SDCC's ".configure", such as when using Visual Studio and msbuild. If you're trying to build on linux or MacOS, or Windows with MSYS2, then you just need a simple build script to use SDCC's ".configure", with settings to tell it to look for include files in the sdcc/include directory. Here's one for a minimal SDCC build. You can play with the configuration options and see where if/when it breaks. As for sdar, sdld, etc ... I...

Treedec and Gala are just header libraries, there is nothing that you need to install to use them, they just go into the sdcc/include/ directory just like the boost headers. What you're going through with your ".configure", "make" and "make install" for these libraries is completely unnecessary if you want to use them locally, and don't wish/need to have them installed into your linux system. It is just like zlib, and libpng, and most other libraries. Yes, you can compile them into dynamically-linked...

Treedec and Gala are just header libraries, there is nothing that you need to install to use them, they just go into the sdcc/include/ directory just like the boost headers. What you're going through with your ".configure", "make" and "make install" for these libraries is completely unnecessary if you want to use them locally, and don't wish/need to have them installed into your linux system. It is just like zlib, and libpng, and most other libraries. Yes, you can compile them into dynamically-linked...

Boost was designed as a library of headers, there are no cpp files required, at least not for SDCC. If you pick entire Boost directories, then you lose the purpose of this list, which is the minimal set of files that SDCC actually uses. My purpose was not to set up a system that can download specific Boost files from the internet, it is to create a simple minimal "sdcc/include/" directory that can be added to the HuC repo and used to build SDCC. As such I do NOT want to chase every small change in...

Boost was designed as a library of headers, there are no cpp files required, at least not for SDCC. If you pick entire Boost directories, then you lose the purpose of this list, which is the minimal set of files that SDCC actually uses. My purpose was not to set up a system that can download specific Boost files from the internet, it is to create a simple minimal "sdcc/include/" directory that can be added to the HuC repo and used to build SDCC. As such I do NOT want to chase every small change in...

Here is what I have, please understand that this has only minimal cleanup for public use. This msbuild "solution" ONLY builds the SDCC compiler itself, and ONLY with the mos6502 port, so I don't think that most people would find it useful. Ger Hobbelt's patches in the PATCHES ticket are presumably closer to what you're looking for. Please note that this also includes a modification to SDCC's version.awk so that the version information is in one place (src/version.h) and not split into two directories...