You need to
before you can comment on or make changes to this bug.
WebCore/platform/FileSystem.h doesn't have a PlatformFileHandle definition for PLATFORM(WIN_OS).
What I wanted was a way to distinguish between the CHROMIUM port on Windows and the CHROMIUM port on Mac/Linux. If I understand the code correctly, there's no way to do this in WebKit, because WebKit knows only about one generic CHROMIUM port. So we'll have to take care of this in the Chromium code.
After talking to Darin, it looks like we can extend the PlatformFileHandle definition for PLATFORM(WIN) to all WebKit ports built on Windows, which seems reasonable to me and works for Chromium too.
Reopening the issue, patch coming shortly.
Created an attachment (id=32399) [details]
(From update of attachment 32399 [details])
I'm concerned this may cause problems for the PLATFORM(QT) build.
I believe that in the PLATFORM(QT) builds on Windows, PLATFORM(WIN_OS)
will also be defined.
You may be able to avoid that problem by revising the #ifdefs to check
for PLATFORM(QT) before checking for PLATFORM(WIN_OS).
Also, the very last PLATFORM(WIN) in FileSystem.h might be best kept
as PLATFORM(WIN). It looks like it is a declaration of additional
functions that perhaps only make sense in the PLATFORM(WIN) port
(i.e., Safari on Windows).
CC'ing folks who seemed to have been involved with the PLATFORM(QT) code in FileSystem.h. Guys, please see comment #4. Thanks!
Created an attachment (id=32401) [details]
(From update of attachment 32401 [details])
This looks like it will work. R=me
Landed as: http://trac.webkit.org/changeset/45640