Tony, I’m not quite sure to understand. tcc.exe, as it is built from Cygwin+Mafile IS a truly standalone binary.
You can copy this binary alone anywhere and you’ll be able to run it: F:\>tcc -v tcc version 0.9.27 (x86_64 Windows) However, as any C compiler I know, you also need to get access to all *.h that your program includes. Of course, when your C files are compiled, you also need to link with C libraries found in .a This is true for VisualC and gcc for example that have many .h and .lib/.a C. From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Tony Papadimitriou Sent: jeudi 23 février 2017 15:27 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] Building TCC statically Hmm, I’ve been thinking whether the related libtcc1.a (32-bit or 64-bit, depending) could also be part of the single stand-alone executable? This would make a compiler that is truly self-contained in a single portable executable, right? From: Christian Jullien <mailto:eli...@orange.fr> Sent: Sunday, February 12, 2017 6:42 PM To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] Building TCC statically The win32/Makefile I pushed today build standalone binaries that require no runtime. You need a working Cygwin toolchain to bootstrap them. Christian From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Tony Papadimitriou Sent: dimanche 12 février 2017 17:20 To: tinycc-devel@nongnu.org Subject: [Tinycc-devel] Building TCC statically Hi, Is is possible to build TCC statically (no LIBTCC.DLL dependency) for Windows so that I have a single stand-alone executable of tcc.exe? If so, please tell me how. Thank you. _____ _______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
_______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
