Page 1 of 1

Current defaults versus non-defaults building Pale Moon?

Posted: Wed, 30 Jan 2019, 02:00
by Walter Dnes
Stuff changes over time, including Pale Moon compile options. Here's most of my mozconfig, customized for my home desktop PC. How much of it is already the default or inapplicable, that I can safely delete?

Code: Select all

ac_add_options --disable-official-branding
export MOZILLA_OFFICIAL=0

mk_add_options MOZ_CO_PROJECT=browser

ac_add_options --enable-application=palemoon
ac_add_options --enable-default-toolkit=cairo-gtk2
ac_add_options --enable-install-strip
ac_add_options --enable-jemalloc
ac_add_options --enable-strip

ac_add_options --disable-accessibility
ac_add_options --disable-crashreporter
ac_add_options --disable-debug
ac_add_options --disable-necko-wifi
ac_add_options --disable-parental-controls
ac_add_options --disable-tests
ac_add_options --disable-updater
ac_add_options --disable-webrtc

ac_add_options --with-branding=application/palemoon/branding/unofficial
ac_add_options --with-pthreads

ac_add_options --x-libraries=/usr/lib64

Re: Current defaults versus non-defaults building Pale Moon?  Topic is solved

Posted: Wed, 30 Jan 2019, 06:12
by New Tobin Paradigm
MOZ_CO_PROJECT hasn't been a ting since Mozilla used CVS.

WebRTC is default not built.. MOZILLA_OFFICIAL should be set or not exist but it should be set.. 0 is different than unset sometimes..

--enable-install-strip likely shouldn't be used.. The rest looks fine to me.

Re: Current defaults versus non-defaults building Pale Moon?

Posted: Wed, 30 Jan 2019, 19:06
by Walter Dnes
Thanks. I'll update the mozconfigs for my notebook and desktop.