# mingw32

- Thread: https://externals.io/message/6110
- Original archive: https://news-web.php.net/php.internals/6110
- Started by Sascha Schumann on 2003-12-03T16:01:23+00:00
- Messages: 5
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #6110 — Sascha Schumann — 2003-12-03T16:01:23+00:00

URL: https://externals.io/message/6110#6110

Hi Wez,

    now that the dependency on VC has been dropped, what would it
    take to get mingw32 build support?

    - Sascha

---

## #6112 — Pierre-Alain Joye — 2003-12-03T16:07:37+00:00

URL: https://externals.io/message/6110#6112 · In reply to: #6110

On Wed, 3 Dec 2003 17:01:23 +0100 (CET)
Sascha Schumann <sascha@schumann.cx> wrote:

>     Hi Wez,
> 
>     now that the dependency on VC has been dropped, what would it
>     take to get mingw32 build support?

Should be really great :).

By the way (or a bit OT), I got little little success by running console
VC tools using wine on linux, anyone experencied with these tools?

pierre

---

## #6115 — Wez Furlong — 2003-12-03T16:38:17+00:00

URL: https://externals.io/message/6110#6115 · In reply to: #6110

When I tried to enable win32 specific extensions (such as COM)
under cygwin, I found that a lot of the win32 api headers were
missing, so the build failed.

I suspect that the same problem will manifest with mingw32.
It's nothing that downloading the platform SDK won't solve,
but if you download that, you've got the MS build tools anyway.

I don't plan to look at mingw32 myself, and I don't want to
deal with patches for it until I've completed the features
I have planned for the build system; once done, adding mingw
support should be reasonably simple (just change the object
and library suffixes and compiler flags...).

--Wez.

>     now that the dependency on VC has been dropped, what would it
>     take to get mingw32 build support?

---

## #6116 — Sascha Schumann — 2003-12-03T16:45:00+00:00

URL: https://externals.io/message/6110#6116 · In reply to: #6115

> When I tried to enable win32 specific extensions (such as COM)
> under cygwin, I found that a lot of the win32 api headers were
> missing, so the build failed.

    Cygwin is a Unix portability layer, not a win32. :)

    mingw's header set should be fairly complete.

    http://www.mingw.org/mingwfaq.shtml#faq-w32api

> I don't plan to look at mingw32 myself, and I don't want to
> deal with patches for it until I've completed the features
> I have planned for the build system; once done, adding mingw
> support should be reasonably simple (just change the object
> and library suffixes and compiler flags...).

    Will there be an abstraction similar to our current m4
    infrastructure? (I have not looked at the .js yet)

    - Sascha

---

## #6117 — Wez Furlong — 2003-12-03T16:48:03+00:00

URL: https://externals.io/message/6110#6117 · In reply to: #6116

> > […]
> 
>     Cygwin is a Unix portability layer, not a win32. :)

Sure, but you can use the win32 api from there, and some of
the headers used by COM are not present in cygwin install.
 
>     Will there be an abstraction similar to our current m4
>     infrastructure? (I have not looked at the .js yet)

Although there isn't right at this moment, there will be.

--Wez.