I recently built Chromium 10 on OpenBSD and Solaris, I'm submitting the ifdef changes that came out of that work. Most of these diffs simply change
OS(LINUX) || OS(FREEBSD)
OS(UNIX) && !OS(DARWIN)
rather than stringing along something like
OS(LINUX) || OS(FREEBSD) || OS(OPENBSD) || OS(SOLARIS) || OS(NETBSD) || OS(DRAGONFLY)
every time support is added for a new Unix. This patch from WebKit trunk was tested on FreeBSD, an earlier variant was tested with Chromium 10 on OpenBSD and Solaris. All ifdef changes are only on files either built for Chromium or that are safe-guarded with a PLATFORM(CHROMIUM), so this patch shouldn't affect non-Chromium platforms. Some of the Skia files aren't built on Darwin so the check for Darwin is left off there. I added OpenBSD and Solaris to the Inspector bindings too.
Created attachment 90876 [details]
Resetting r? flag since you're asking for review.
Comment on attachment 90876 [details]
View in context: https://bugs.webkit.org/attachment.cgi?id=90876&action=review
> + patch for inclusive Unix support on Chromium
> + https://bugs.webkit.org/show_bug.cgi?id=59297
This should go in WebKit/chromium/ChangeLog. The prepare-ChangeLog and webkit-patch scripts will place changelogs in the proper locations.
"inclusive Unix support" is pretty vague - can you state what you actually mean?
Created attachment 91035 [details]
Sorry about setting the wrong review flag, I didn't read the instructions properly. I didn't see the ChangeLog in WebKit/chromium, fixed that and updated the message with more detail. What directory is one supposed to run prepare-ChangeLog from in a Chromium checkout of WebKit? I tried running from third_party/WebKit/Source but it wouldn't work, which is why I found the ChangeLog directories myself and ran it from each one separately. As for what I meant by inclusive support, I described it in the first comment here and have updated the comment in the ChangeLog. Let me know if it isn't clear.
Comment on attachment 91035 [details]
View in context: https://bugs.webkit.org/attachment.cgi?id=91035&action=review
> + No new tests. (OOPS!)
Nit: This should be replaced with a line that says why there are no new tests (e.g., No new tests since this is just a compile change.). I will fix this when I check it in.