Henrik Schröder wrote:
As far as I understand it, building with MinGW results in stand-alone
executables, as opposed to building with Cygwin, which creates
dependencies to cygwin.dll. None of them requires some sort of runtime
though, that would be absolutely horrible. :-)
I was looking at this recently, and they do make references to a MinGW
"runtime", but I think their definition is the minimal set of DLLs
required to give the Microsoft C shipped libraries support for C99 and
other standards MinGW implements. I'm guessing that you implied a
process or something as "runtime".
All the windows versions I've used have been stand-alone executables
that you could run with parameters like usual, or pass some
windows-specific parameters telling it to install itself as a service.
I like that model, I mean it's a 80kB command-line executable, it
really doesn't have to be more complicated than that.
+1.
I think all of this, including Windows service description, can be
easily packaged so the Windows user doesn't need to be too concerned
with the details. It'll be incumbent upon the memcached development
community to test compatibility with MinGW and various versions of
Windows, but for something like memcached it doesn't sound too hard or
risky.
- Matt
/Henrik
On Tue, Nov 3, 2009 at 13:20, Trond Norbye <[email protected]
<mailto:[email protected]>> wrote:
Do you need to install a runtime to run a binary compiled with
MinGW, or is there just one binary we need to release?
If we can release a single binary that a user can download "we"
(aka the community) could provide a binary for each release to
ease the pain for the average windows developer...
Cheers,
Trond
