Comment # 79
on bug 7893
from Guy Harris
(In reply to comment #77)
> Windows use ./configure too, right?
No. It requires manual configuration by modifying the top-level config.nmake
file; it's only one operating system (and even when it was two - Windows OT and
Windows NT - they were sufficiently similar that we didn't worry much about the
difference), not the twisty little maze of OSes, all slightly different, that
are the UN*Xes, and we have to supply almost all of the support libraries so we
don't have to worry about whether the OS supplies them and what version they
supply, so manual configuration isn't as painful as it would be on UN*X.
And even on UN*X we also support CMake.
Equally importantly, Windows's rules for linking aren't exactly the same as the
rules that most if not all UN*Xes use; the whole reason WS_DLL_PUBLIC exists is
that the rules for exporting functions and data from dynamically-linked
libraries and importing them into code that uses those libraries are more
complicated on Windows than on UN*X (most UN*X dynamic linking implementations
are modeled after the SunOS 4.x one or its SVR4 descendant, and that one was
designed to be as similar as possible to the way static linking worked).
You are receiving this mail because:
- You are watching all bug changes.