NightStrike wrote:
You could use what we provide with tinycc, and likewise still have a
small footprint.
I would say that out of the box support for TINYC in the mingw
headers could of course be a nice option (avoiding the notorious
#define __attribute__ unless __GNUC__ for example to
start w
On Sun, Sep 19, 2021, 04:36 Christian Jullien wrote:
> The nice thing with tcc is that it is fast … but also Tiny.
>
> Once compiled it can be used on any Windows machine not bloated with
> Gigabytes of memory like VC++, Cygwin or Mingw64.
>
Mingw-w64 does not itself require any memory at all. W
and the stuff is now part of
gnumake trunk.
C.
From: pursuer2 [mailto:pursu...@qq.com]
Sent: Sunday, September 19, 2021 11:38
To: jullien; tinycc-devel
Subject: Re: [Tinycc-devel] Outdated .def files
In my opinion, as tcc do not offer the complete libc on unix-like os,
Current Windows
In my opinion, as tcc do not offer the complete libc on unix-like os, Current
Windows support in tcc which help tcc compile itself is enough. We can
recommand user to use tcc with compatible c library (like
"mingw","msvc","windows sdk"?) for other os-dependent feature.
I'm not familiar with Wi
if you like. It may be part of tcc front end like "tcc
-mt" similar to "tcc -ar"
Christian
-Original Message-
From: grischka [mailto:gris...@gmx.de]
Sent: Saturday, September 18, 2021 21:02
To: jull...@eligis.com; tinycc-devel@nongnu.org
Subject: Re: [Tinycc-devel]
Christian Jullien wrote:
Hi Grischka,
I fact I processed differently. I was very disappointed to see that my code
compiled by tcc reported "Windows 10" on "Windows 11" because kernel32.def
lacks the few API I recently added for this purpose.
As far as I can see, "Windows 11" identifies itself
projects to define them differently.
> -Original Message-
> From: grischka [mailto:gris...@gmx.de]
> Sent: Saturday, September 18, 2021 14:06
> To: jull...@eligis.com; tinycc-devel@nongnu.org
> Subject: Re: [Tinycc-devel] Outdated .def files
>
> Christian Jullien wrote:
ves more
choices.
C.
-Original Message-
From: grischka [mailto:gris...@gmx.de]
Sent: Saturday, September 18, 2021 14:06
To: jull...@eligis.com; tinycc-devel@nongnu.org
Subject: Re: [Tinycc-devel] Outdated .def files
Christian Jullien wrote:
> Hi,
> If I regenerate a kernel32.def out of kernel32
Christian Jullien wrote:
Hi,
If I regenerate a kernel32.def out of kernel32.dll on my Windows 10 21H1
machine it is 3x times bigger that the one that currently comes with
tcc. (see enclosed)
It means many kernel32 API are not directly available for tcc.
It is probably the same with other .def f
declaration and use the
associated definition in kernel32.def
M2c
From: avih [mailto:avih...@yahoo.com]
Sent: Saturday, September 18, 2021 08:09
To: tinycc-devel@nongnu.org; jull...@eligis.com
Subject: Re: [Tinycc-devel] Outdated .def files
I _think_ the current win32 definitions are from
I _think_ the current win32 definitions are from Windows XP.
If we update to newer definitions, then I assume it would compile
successfully programs which use newer APIs, but the question is
what happens at runtime.
mingw has a system to define what to target (I don't recall the
specifics), so u
Hi,
If I regenerate a kernel32.def out of kernel32.dll on my Windows 10 21H1
machine it is 3x times bigger that the one that currently comes with tcc.
(see enclosed)
It means many kernel32 API are not directly available for tcc.
It is probably the same with other .def files
What do you
12 matches
Mail list logo
