OK, I'm planning to go with the borrowed 32-bit Ubuntu libs for nss, nspr, and sqlite. These libs won't go in our source tree, but will magically appear from somewhere at packaging time (in reality, probably just pulled from the build host, since that's already configured properly). This will add a bit more than 1MB to the download, at least the first time. When installed, they'll live in the chromium directory and be invoked through a chromium wrapper script with LD_LIBRARY_PATH. This is subject to change with something more elegant/robust, but that should be good enough to start dogfooding. Please let me know if there are any objections.
Michael On Thu, Feb 26, 2009 at 10:54 AM, Michael Moss <[email protected]> wrote: > On Thu, Feb 26, 2009 at 10:40 AM, Dean McNamee <[email protected]> wrote: >> >> We don't need to stick the .so's in /usr/lib32 then do we? We can >> stick them in our own directory if that's the concern. I don't >> understand have this relates to building our own .so's or reusing >> someone elses, since either way you have the problem of us shipping >> one, and someone might already have one. > > I think we're in agreement here, but I was more just arguing against > the separate package dependency. If it's installing to our directory, > it might as well not be a separate package. > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
