Index: README.md |
=================================================================== |
--- a/README.md |
+++ b/README.md |
@@ -24,9 +24,11 @@ |
./build.py -t chrome build -k adblockpluschrome.pem |
./build.py -t safari build -k adblockplussafari.pem |
+ ./build.py -t edge build |
This will create a build with a name in the form |
-_adblockpluschrome-1.2.3.nnnn.crx_ or _adblockplussafari-1.2.3.nnnn.safariextz_. |
+_adblockpluschrome-1.2.3.nnnn.crx_, _adblockplussafari-1.2.3.nnnn.safariextz_ |
+or adblockplusedge-1.2.3.nnnn.appx. |
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. Safari on the other |
hand always requires a valid developer certificate, you need to get one in the |
@@ -48,6 +50,10 @@ |
changes to the source code re-run the command to update the development |
environment, the extension should reload automatically after a few seconds. |
+For Edge you can use the same development environment as Chrome. You should load |
+_devenv.chrome_ as unpacked extension directory. After rebuilding the extension |
kzar
2016/12/01 14:23:06
Nit: Missing a word "as AN unpacked extension dire
|
+you should usually force reloading it in Edge. |
+ |
In Safari you should load _devenv.safari/adblockplussafari.safariextension_ as |
unpacked extension directory. After making changes to the source code re-run the |
command to update the development environment. You will still need to reload the |