Re: Firefox 38.8.0 Beta 7 released
Dave Yeo <[email protected]>
| Newsgroups | gmane.comp.mozilla.devel.os2 |
|---|---|
| Message-ID | <[email protected]> |
Doug Bissett wrote: > Since you can't get a good internet connection, perhaps you need to do > the footwork, and distribute a DIFF file so that somebody with a good > connection can do the build and upload thing. It would probably take a > bit of work to get that set up, but I suspect that your wife would be > happier. The code is at https://bitbucket.org/dryeo/dry-comm-esr31, https://github.com/bitwiseworks/mozilla-os2/ and a couple of other places, eg chatzilla needs to be pulled in along with a couple of other extensions and LDAP with the LDAP diffs in the main repository. Dmiks directions for building Firefox mostly applies to SM, TB and IM, especially the prerequisites. I'll try to update my BUILD.OS2 and mozconfigs tonight and if anyone wants to try to build... > > FWIW, I would like to see a statically linked version of FF (at > least), just because I am running out of shared memory space, and I am > also running out of ways to solve the problem. Currently, I cannot run > FF and TB at the same time, without crashing one, both, or something > else (fortunately, I use PMMail, which doesn't use very much shared > memory space). Statically linking still means linking things into xul.dll, which won't help your shared memory problem. Here I can run FF, SM, and TB for a couple of days before the system traps. I mark all the DLLs to load high and lately I've been sharing the DLLs when the apps are built from the same tree. Due to calendar, I have to start TB first and then SM and FF happily use the same DLLs that TB loaded. I just revisited which DLLs can be statically linked in, and actually it isn't too many. Fontconfig and Pango are only available as DLLs (I built FF with a static Pango at one point, had a browser with no text) and while they can be rebuilt to statically link in their dependencies, its work, the binaries need hosting somewhere along with their source for licensing reasons. Ideally would be to build with the -bstatic flag but its broken on our platform. > > BitWise is building the dynamically linked version, so let them do > that, and concentrate on a statically linked version. Many of us would > be grateful. Dave