Changeset f72a04a
- Timestamp:
- 05/19/2012 09:07:55 PM (12 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 8cf877e1
- Parents:
- 37aba7f
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
xsoft/graphweb/firefox.xml
r37aba7f rf72a04a 12 12 <!ENTITY firefox-size "75 MB"> 13 13 <!ENTITY firefox-buildsize "2.8 GB (31 MB installed)"> 14 <!ENTITY firefox-time "24 SBU ">14 <!ENTITY firefox-time "24 SBU (0.3 SBU if using xulrunner)"> 15 15 ]> 16 16 … … 79 79 <xref linkend="alsa-lib"/>, 80 80 <xref linkend="gtk2"/>, 81 <xref linkend="zip"/> and81 <xref linkend="zip"/>, and 82 82 <xref linkend="unzip"/>. 83 83 </para> … … 105 105 <ulink url="http://www.valgrind.org/">Valgrind</ulink> (only for testing 106 106 the jemalloc code), 107 <xref linkend="wget"/> and107 <xref linkend="wget"/>, and 108 108 <xref linkend="xulrunner"/> 109 109 </para> … … 116 116 <sect2 role="installation"> 117 117 <title>Installation of Firefox</title> 118 119 <para> 120 There are two major methods for building <application>Firefox</application>. 121 In the standard case, the entire suite of libraries is built and 122 installed. In the other, most of the system is built using the procedures 123 found in <xref linkend="xulrunner"/>. This is advantageous if you 124 are planning to build other related packages such as <xref linkend="icedtea-web"/>, 125 <xref linkend="seamonkey"/>, or <xref linkend="thunderbird"/>. With 126 either build method, you need to run the main build procedure below with 127 the appropriate options in the <filename>mozconfig</filename> file. Then 128 use the appropriate instructions depending on the chosen build method. 129 </para> 118 130 119 131 <para>
Note:
See TracChangeset
for help on using the changeset viewer.