By the way, since this apparently hasn't been discussed as widely as I had thought, here's a little background on this new nss/nspr stuff. We currently build Linux Chromium with the system nss and nspr libraries. This works fine for most 32-bit distros, since these are standard packages, and that allows us to leverage the distro for critical security updates. This functionality is not going away; it will still be possible to build against the system versions of these libs, and this is how we expect distro maintainers will build their packages. However, our own target platform of 64-bit Ubuntu Hardy doesn't provide these libraries in 32-bit form, so Chromium won't run on an unmodified version of that distro (note the hoops our Linux development instructions jump through to setup a build machine). To support dogfooding on our target platform, and to provide a compatibility option for 64-bit distros in general, we decided to include nss and nspr directly in our build, thus bypassing any issues with missing system libs.
Michael On Wed, Feb 25, 2009 at 5:04 PM, Thomas Van Lenten <[email protected]> wrote: > Sorry for arriving late w/ this question... > > I'm guessing NSS & NSPR are needed for the linux build? Should they be > pulled in via DEPS instead of being directly in src/third_party? In the > current form it causes both mac and windows to have to add ~80M to their svn > trees that really isn't needed. > > TVL > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
