Re: [Tinycc-devel] Outdated .def files

[Christian Jullien]

If I use recent VC++ on Windows 10, I can limit myself to the set of API supported by XP and the result will (should) run on Windows XP.

If I however use specific Windows 10 API, it will hand on XP.

 

My opinion is that tcc should use a recent (latest?) kernel32.def and let the user decide what subset he supports.

 

In theory, _WIN32_WINNT should limit the subset an application can see by giving only the definitions available for a given version. I’m far from certain that our .h is aware of the different definitions.

A least a tcc developer will be able to supply its own declaration and use the associated definition in kernel32.def

 

M2c

 

From: avih [mailto:avihpit@yahoo.com]
Sent: Saturday, September 18, 2021 08:09
To: tinycc-devel@nongnu.org; jullien@eligis.com
Subject: Re: [Tinycc-devel] Outdated .def files

 

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 unless tcc's mingw files already have it, I think
it would need to be added, or at least considered.

- avih

On Saturday, September 18, 2021, 09:03:12 AM GMT+3, Christian Jullien <eligis@orange.fr> 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 files

 

What do you advice ?

 

 

_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel