Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of trawick@gmail.com designates
 209.85.214.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=tZBSBU6MniOWrn+BmKM44Z2aMDC8WRZmayf2qmWo3ag81v4xEXWJ1F2E8k38XHsKGO
         6UlgQS0LYQahbwyget6GpEYH4jkVzxElwT3wdRaUcF5GxkhBITt/mdTAKkYyISDsuwed
         +CPk8mynjrOwmSyTU/3CoMbTv3y83acEwF5hs=
MIME-Version: 1.0
Date: Thu, 14 Apr 2011 10:45:33 -0400
Message-ID: <BANLkTimFzkOW76juv=8F+7pNY51R2zANXQ@mail.gmail.com>
Subject: Status of MinGW (httpd)
From: Jeff Trawick <trawick@gmail.com>
To: dev@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1

I know others have played on MinGW before, but I don't know how long
ago or what was attempted.  Here are my observations:

Trunk:

I've been building/running this with shared library builds of apr trunk.

* Only statically linked modules work AFAIK.
* If you build any of the modules that have their own
foo_DECLARE_EXPORT logic you need to add foo_DECLARE_EXPORT to
CPPFLAGS (kludge).
* I haven't tried with many different modules, especially not with
those which require extra third-party libraries (OpenSSL, Lua, etc.).
* There's a trunk-specific problem linking to PCRE because the PCRE
libs are specified within LDFLAGS; I don't have a fix for this yet,
and use a hack to relink it with "-L/path/to/pcre -lpcre" moved to a
later point in the command.

2.2.18-dev:

I've been building/running this with static library builds of apr
1.4.x/apr-util 1.3.x.

Differences from trunk:

* pcre linking problem does not exist (no issue)
* needs a couple of patches listed in STATUS to build practically
(each needs one more vote)
* needs another patch I'll post later to clean up boatloads of gcc
warnings in Windows code which drive some people crazy