This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Cygwin support
- From: Steinar Bang <sb at dod dot no>
- To: gcc at gcc dot gnu dot org
- Date: Mon, 19 Jan 2009 12:23:56 +0100
- Subject: Re: Cygwin support
- References: <c7d922350811140136u4fe6ebdeh457b7efaae713613@mail.gmail.com> <491D6B7F.58BB640A@dessent.net> <200811141258.41308.paul@codesourcery.com> <491DA33D.AAD3C762@dessent.net> <491DA605.5000308@redhat.com> <491DAB8E.BCD682DC@dessent.net> <Pine.LNX.4.64.0811141652020.11731@digraph.polyomino.org.uk> <491DC5AC.DB128F8A@dessent.net>
>>>>> Brian Dessent <brian@dessent.net>:
[snip! Access from plugins to every aspect of the compiler]
> ... This means you'd have to move essentially everything into this
> mega-DLL, leaving cc1 and friends as merely stubs that set a flag and
> then call into the DLL never to return, since anything left in cc1
> would not be accessible from the plugin.
FWIW this is not an uncommon situation for Win32 executables, especially
for multiplatform application and/or applications ported from unix.