Index: xsoft/graphweb/firefox.xml
===================================================================
--- xsoft/graphweb/firefox.xml (revision 44cd41edb3b52b071d3e276b0e8f0f29a36cbb88)
+++ xsoft/graphweb/firefox.xml (revision 2bd2dcee41bd94bad6503d85a0486d42d70d07d1)
@@ -11,6 +11,9 @@
-
-
+
+
+
]>
@@ -154,5 +157,5 @@
Recommended
- ,
+
,
,
@@ -243,7 +246,7 @@
ac_add_options --disable-gconf
-# Uncomment this if you have not installed nodejs
-# but note that nodejs will be required in firefox-64
-#ac_add_options --disable-nodejs
+# Uncomment this if you have not installed nodejs,
+# but note that nodejs will be required in firefox-64
+#ac_add_options --disable-nodejs
# From firefox-61, the stylo CSS code can no-longer be disabled
@@ -256,5 +259,13 @@
ac_add_options --with-system-nspr
ac_add_options --with-system-nss
-ac_add_options --with-system-icu
+
+# Only enable system icu if the version is 61 or 62
+#ac_add_options --with-system-icu
+
+# The gold linker is no-longer the default
+ac_add_options --enable-linker=gold
+
+# You cannot distribute the binary if you do this
+ac_add_options --enable-official-branding
# If you are going to apply the patch for system graphite
@@ -280,6 +291,4 @@
# Optimization for size is broken with gcc7 and later
ac_add_options --enable-optimize="-O2"
-
-ac_add_options --enable-official-branding
# From firefox-61 system cairo is not supported
@@ -345,5 +354,7 @@
-./mach build
+export CC=clang CXX=clang++ AR=llvm-ar NM=llvm-nm RANLIB=llvm-ranlib &&
+./mach build &&
+unset CC CXX AR NM RANLIB
@@ -382,4 +393,10 @@
+ export CC=clang CXX=clang++ ...: Upstream now use
+ clang and building with any recent version
+ saves a lot of space.
+
+
+ ./mach build: Firefox
now uses this python2 script to run the
@@ -391,4 +408,16 @@
need details of which files are being compiled, together with any C or
C++ flags being used.
+
+
+
+ : In theory, mach
+ will use the number of online CPU cores - but on some machines the bulk
+ of the build will drag on as if only 1 core is present. Specifying the
+ number of jobs (4 in this example) fixes that. Unlike traditional
+ recommendations for running make, the exact number
+ of cores is usually fastest - exceptionally, N+1 may be better on a
+ well-specified modern machine. But do NOT use this if building from a
+ term where taskset has been used to restrict the
+ available cores.