I forgot to mention - there's a single file that may not be complete, base/crypto/signature_verifier_nss.cc - this is because the FreeBSD port of NSS is too old and doesn't have a function it needs. I'll get to that at some point soon, but I don't anticipate it being a problem.
On Thu, Aug 27, 2009 at 10:57 AM, Ben Laurie<[email protected]> wrote: > As brettw requested, I ported chrome/browser/renderer_host/ and base/. > This is now done and can be reviewed here: > > http://codereview.chromium.org/172032 > > The description summarises the changes I made, what do people think? > (I haven't forgot that I said I'd document defines - I'll do that once > people are happy with them) > > Added USE_GDK, set when either TOOLKIT_GTK or TOOLKIT_VIEWS is set but > not OS_WIN. > > Added USE_X11. Set when OS_LINUX or OS_FREEBSD is set. > > Added USE_BASE_DATA_PACK for base::DataPack usage, set for OS_MACOSX, > OS_LINUX or OS_FREEBSD. > > Added USE_NSS for ... nss (for crypto). Windows and MacOS use > platform-specific libraries. > > All of the above cause slightly odd formulations like: > > #if defined(OS_WIN) > ... > #elif defined(USE_BASE_DATA_PACK) > ... > #endif > > Possibly should also define USE_DLL_FOR_DATA, etc? Or something? > > Wrapped various references to struct stat64 and stat64() to use struct > stat and stat() for FreeBSD - but a "man stat64" on Linux suggests > that we could do the same thing for at least Linux, too, and perhaps > eliminate the wrapper? > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
