[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tinycc-devel] Could someone please augment tcc development tree wit
Re: [Tinycc-devel] Could someone please augment tcc development tree with this?
Fri, 30 Mar 2012 23:52:48 -0400
The files are a header file and a .def file that presumably allows tcc to link against winmm.dll, a multimedia support library on Windows. The "extracted" part refers to the header and def information, not the code, so I don't think copyright issues as at play.
I am also curious what is the community attitude on how to link to various system libraries. Should we start including various platform specific headers?
On 30 March 2012 23:13, Jared Maddox <address@hidden>
> Date: Fri, 30 Mar 2012 16:28:13 -0700 (PDT)
> From: Lance Mason <address@hidden>
> To: address@hidden
> Subject: [Tinycc-devel] Could someone please augment tcc development
> tree with this?
> Content-Type: text/plain; charset="us-ascii"
>What is it, where did you get it, how did you get it?
> Could someone please augment tcc development tree with this?
> I am sure the slightly modified files are correct for the current version of
> It was extracted from an early Windows XP DLL so it should work for
> all important versions of Windows.
To a certain extent, things can be legally reverse-engineered without
permission (example: you can read the linker table from a dll to
figure out what symbols it provides, do research on those symbols
online, & use that to create a replacement dll), but there are also
restrictions (you cannot normally convert a dll into assembly code,
and base your replacement on THAT, because the binary machoine code is
not considered 'public', while the linker tables have to be public to
work at all).
Depending on where you got it, and how, it might be something that
CANNOT be added to TCC.
I say all this because "extracted from an early Windows XP DLL" makes
Tinycc-devel mailing list