[Ntop-dev] Patches and documentation for building ntop on MingW
Burton at ntopSupport.com
Wed Aug 31 13:53:51 CEST 2005
Nope... Same/similar effect, different mechanism, but both are really shims.
Cygwin provides a DLL which accepts the Unix calls and does the translation
to Win32 equivalents.
MinGW provides in-line code which accepts the Unix calls and does the
translation to Win32 equivalents.
"MinGW: A collection of freely available and freely distributable Windows
specific header files and import libraries combined with GNU toolsets that
allow one to produce native Windows programs that do not rely on any
3rd-party C runtime DLLs."
So MinGW says it's 'native' code, but only in the sense that it doesn't
require the DLL. The translation of Unix API to/from Win32 API still has to
happen. Difference from Cygwin is that a lot of this happens in the
Call them translators, shims, whatever - the technology is quite similar
(and yet quite different).
From: ntop-dev-bounces at unipi.it [mailto:ntop-dev-bounces at unipi.it] On Behalf
Of Gisle Vanem
Sent: Wednesday, August 31, 2005 6:22 AM
To: ntop-dev at Unipi.IT
Subject: Re: [Ntop-dev] Patches and documentation for building ntop on MingW
"Burton Strauss" wrote:
> Once again, MinGW is a compatibility layer (shim)
It is? What shimming is done in MingW? You must be thinking about CygWin.
Ntop-dev mailing list
Ntop-dev at unipi.it
More information about the Ntop-dev