Build release from source, override xpi signing requirement

Add-ons Development
#1

Hi,

I’m building Firefox from source because I made a modification.
I’ve updated to the most recent release: 51.0.2 (64-bit).
The problem I’m facing is that I can no longer install unsigned addons.
I’ve tried setting xpinstall.signatures.required to false, but this still doesn’t allow me to install my addon.

How can I re-enable this functionality on a custom build from the mozilla-release repository?
The funny thing is that when building I already get a non-branded version of Firefox, named Nightly.
So I was under the impression unbranded builds would allow installing unsigned addons.
But it’s not working for me.

Thanks in advance.

#2

Maybe someone on #firefox or #build in the Mozilla IRC can point you to the right configuration options to enable the preference.

#3

Great idea! Never used IRC before but I got the answer I needed:

RyanVM user: https://dxr.mozilla.org/mozilla-central/source/browser/config/mozconfigs/win32/add-on-devel are the extra config options set for the unbranded builds we ship
RyanVM MOZ_REQUIRE_SIGNING=0 looks like the most relevant one there
RyanVM yeah, that should do it
RyanVM https://dxr.mozilla.org/mozilla-central/source/build/mozconfig.common#22 (trunk) vs. https://dxr.mozilla.org/mozilla-release/source/build/mozconfig.common#22 (release)
RyanVM value gets flipped going from aurora->beta

I’ve added MOZ_REQUIRE_SIGNING=0 to my .mozconfig file. After a successful build I could install my unsigned addon. I thought that because my build was already unbranded, installing unsigned addons should already work. But apparently there’s a specific build option for that :slight_smile: