On Wed, Aug 19, 2009 at 6:00 PM, Dean McNamee<[email protected]> wrote: > > I kinda feel like this is one of those things you can try hard to > premeditate, but in the end you'll just have to deal with it being > ugly for a while and hope it eventually converges to something better.
The changes in the bulk of the Chrome code are pretty easy to tell in advance. Just search for OS_LINUX. It would be nice if the first pass didn't just tack on OS_FREEBSD to every OS_LINUX in chrome, especially since I think there's a good chance it won't be maintained longer-term. I definitely believe you that there will be a bunch of unknown build/third_party stuff. > Sort of a non-answer, but I'd be happy to see this running on a BSD > first, and then we can argue about the patch. Are you suggesting getting it running before checking anything in? I think BenL's was planning to do it piecemeal. > I just went through some work trying to build it on OpenBSD (promised > a friend I'd try). There are a lot of little things we need to do > before we even have this debated. Pretty much everything in > third_party (icu, libevent), gmock, etc. Some of these will probably > require changes upstream. Interesting, thanks for the information. Brett --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
