Hi, nice additiong, you could have used InnoSetup instead though. I don't really see the point since a portable installation is already quite easy to deal with (minus the PATH part).
https://github.com/Kochise/tinycc_win32 The main problem, you have put your finger on, is the age of the current public build, and the instability of the current mob branch. Regards. ----- Mail d'origine ----- De: Charles Lohr <loh...@gmail.com> À: tinycc-devel@nongnu.org Envoyé: Wed, 02 Nov 2022 19:57:36 +0100 (CET) Objet: [Tinycc-devel] Windows distribution/installer A few days ago, I started experimenting with just using NSIS to package up TinyCC as an installer for Windows, which worked out well. It basically: * Includes TinyCC Win-64 0.9.27 (Boy would a new release be nice!) * Includes Win API Headers Full * Optionally adds TCC (wherever it is installed) to the system path. A few friends have tested it out and it seems to work for them. https://github.com/cnlohr/tinycc-win64-installer A few comments that came up in discussion was: 1) Are there any issues with this? Is anyone upset by the idea of a third-party installer? 2) Is it reasonable to have a non-project-sponsored-installer? Would TCC be consider making a first party installer instead? 3) It would be really useful to include some sort of Make, even if primitive. 4) It would be nice to include some common single-file headers. Since TCC is still a daily driver of mine for some in-work and many outside-of-work projects, I have a lot of interest in this. I also do a lot of C stuff publicly, and people always want to know how to install a C environment. I just wanted to get the conversation started, to see if anyone has any opinions. _______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
