Bug 5614 – version(Win32) vs version(Windows) in Phobos
Status
RESOLVED
Resolution
FIXED
Severity
normal
Priority
P2
Component
phobos
Product
D
Version
D2
Platform
x86_64
OS
Windows
Creation time
2011-02-19T08:23:00Z
Last change time
2012-01-21T18:41:51Z
Assigned to
nobody
Creator
webby
Comments
Comment #0 by webby — 2011-02-19T08:23:08Z
If you try to compile various things in Phobos using -m64 on Windows, you get various build failures which appear to be down to various std files doing things in version(Win32) blocks, when 64bit builds only define 'Win64'.
e.g.
line 28 of std.file imports various things for version(Win32), but later tries to use those imports in version(Windows) blocks.
std.__fileinit declares and sets up 'useWfuncs' in a 'Win32' block. In this case, can it be assumed that the Wide functions are always present in 64bit builds?
std.system sets 'Family' to Win32 in 32bit builds, and asserts in 64bit builds. I'm not sure if this needs a Win64 family or not?
std.stream, std.mmfile, and std.c.stdio all have similar issues.
I know that 64bit support on Windows is some way off, but it would be nice if the front end stuff built at least.