|Subject:||Re: [Tinycc-devel] issues/questions with stddef.h which comes with tcc|
|Date:||Fri, 1 Jan 2021 18:12:41 +0100|
The Windows case is more clear to me, as windows does not have compiler hence no standard includes, the win32/include part contains all the stuff to let tcc find its includes (most of its includes). It contains std C headers and the most common windows headers.
My concern is with includes that are installed with “make install” and go to /usr/local/lib/tcc by default.
From: Joshua Scholar [mailto:firstname.lastname@example.org]
I noticed that in the win32 directory there are 46 include files in the main include directory, 9 in include/sys, there's a secure api directory with 12 files, an a libtcc directory with an include file and a def file.. but the include directory for the non-windows build only has 9 files, so I guess it's relying on the system to have another C compiler installed whose .h files it can use. I haven't been here long, but it does sound like a bad idea to not include your own include files for every platform.
Does that mean you have to have GCC installed? It's awfully confident of them to be sure that every GCC include tree will work. Does Clang work? Is it a license issue? If so, that's passing the license issue on to you.
On Fri, Jan 1, 2021 at 7:45 AM Christian Jullien <email@example.com> wrote:
|[Prev in Thread]||Current Thread||[Next in Thread]|