Noissue - Specify Firefox builds in the README

README.md

Index: README.md
===================================================================
--- a/README.md
+++ b/README.md
@@ -1,11 +1,17 @@
-Adblock Plus for Chrome and Opera
-=================================
+Adblock Plus for Chrome, Opera and Firefox
+==========================================
 
 This repository contains the platform-specific Adblock Plus source code for
-Chrome and Opera. It can be used to build Adblock Plus for these platforms,
-generic Adblock Plus code will be extracted from other repositories
+Chrome, Opera and Firefox. It can be used to build Adblock Plus for these
+platforms, generic Adblock Plus code will be extracted from other repositories
 automatically (see _dependencies_ file).
 
+Note that the Firefox extension built from this repository is the new
+[WebExtension](https://developer.mozilla.org/en-US/Add-ons/WebExtensions).
+The source code of the legacy Adblock Plus extension, based on the now
+deprecated [Add-on SDK](https://developer.mozilla.org/en-US/Add-ons/SDK),

[Wladimir Palant, 2017/06/07 19:54:07]

It's not based on the Add-on SDK, it's rather a plain bootstrapped extension.

[Sebastian Noack, 2017/06/08 13:37:00]

Done.

+can be found [here](https://hg.adblockplus.org/adblockplus).
+
 Building
 ---------
 
@@ -19,24 +25,32 @@
 
 ### Building the extension
 
-Run the following command in the project directory:
+Run one of the following commands in the project directory, depending on your
+target platform:
 
     ./build.py -t chrome build -k adblockpluschrome.pem
+    ./build.py -t gecko-webext build
 
 This will create a build with a name in the form
-_adblockpluschrome-1.2.3.nnnn.crx_
+_adblockpluschrome-1.2.3.nnnn.crx_ or _adblockplusfirefox-1.2.3.nnnn.xpi_
+
 Note that you don't need an existing signing key for Chrome, a new key
 will be created automatically if the file doesn't exist.
 
+The Firefox extension will be unsigned, and therefore cannot be loaded directly
+in Firefox, but is supposed to be uploaded to Mozilla add-ons.

[Wladimir Palant, 2017/06/07 19:54:07]

Unsigned extensions can be installed temporarily via about:debugging, or by
disabling signing requirements (in Nightly). So it's probably better to note
that it can be used for testing but there are more convenient ways (explained
below). Also, it is "Mozilla Add-ons" (with a capital A).

[Sebastian Noack, 2017/06/08 13:37:00]

Done.

+
 ### Development environment
 
 To simplify the process of testing your changes you can create an unpacked
-development environment. For that run the following command:
+development environment. For that run one of the following commands:
 
     ./build.py -t chrome devenv
+    ./build.py -t gecko-webext devenv
 
-This will create a _devenv.chrome_ directory in the repository. In Chrome you
-should load the directory as an unpacked extension. After making changes to the
+This will create a _devenv.*_ directory in the repository. You can load the
+directory as an unpacked extension, under _chrome://extensions_ in Chrome,
+or under _about:debugging_ in Firefox. After making changes to the
 source code re-run the command to update the development environment, the
 extension should reload automatically after a few seconds.