README.md - Issue 29350286: Issue 4376 - Updated buildtools dependency

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments.

Keyboard Shortcuts

	File
u :	up to issue
m :	publish + mail comments
M :	edit review message
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line
<Enter> :	respond to / edit current comment
d :	mark current comment as done

	Issue
u :	up to list of issues
m :	publish + mail comments
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue
# :	close issue

	Comment/message editing
<Ctrl> + s or <Ctrl> + Enter :	save comment
<Esc> :	cancel edit

Side by Side Diff: README.md

Issue 29350286: Issue 4376 - Updated buildtools dependency (Closed)

Patch Set: Rebased, set revisions, tidy up metadata.safari Created Sept. 9, 2016, 3:03 p.m.

Left:
Right:

Use n/p to move between diff chunks; N/P to move between comments.

Jump to:

View unified diff | Download patch

« no previous file with comments | « no previous file | dependencies » ('j') | no next file with comments »

OLD	NEW
1 Adblock Plus for Chrome, Opera and Safari	1 Adblock Plus for Chrome, Opera and Safari

2 =========================================	2 =========================================

3	3

4 This repository contains the platform-specific Adblock Plus source code for	4 This repository contains the platform-specific Adblock Plus source code for

5 Chrome, Opera and Safari. It can be used to build Adblock Plus for these	5 Chrome, Opera and Safari. It can be used to build Adblock Plus for these

6 platforms, generic Adblock Plus code will be extracted from other repositories	6 platforms, generic Adblock Plus code will be extracted from other repositories

7 automatically (see _dependencies_ file).	7 automatically (see _dependencies_ file).

8	8

9 Building	9 Building

10 ---------	10 ---------

11	11

12 ### Requirements	12 ### Requirements

13	13

14 - [Mercurial](https://www.mercurial-scm.org/) or [Git](https://git-scm.com/) (wh ichever you used to clone this repository)	14 - [Mercurial](https://www.mercurial-scm.org/) or [Git](https://git-scm.com/) (wh ichever you used to clone this repository)

15 - [Python 2.7](https://www.python.org)	15 - [Python 2.7](https://www.python.org)

16 - [The Jinja2 module](http://jinja.pocoo.org/docs)	16 - [The Jinja2 module](http://jinja.pocoo.org/docs)

17 - [The PIL module](http://www.pythonware.com/products/pil/)	17 - [The PIL module](http://www.pythonware.com/products/pil/)

18 - For signed Chrome builds: [M2Crypto module](https://github.com/martinpaljak/M2 Crypto)	18 - For signed builds: [PyCrypto module](https://www.dlitz.net/software/pycrypto/)

19 - For signed Safari builds: A [patched version of the xar command line tool](htt ps://github.com/mackyle/xar/)

20	19

21 ### Building the extension	20 ### Building the extension

22	21

23 Run one of the following commands in the project directory, depending on your	22 Run one of the following commands in the project directory, depending on your

24 target platform:	23 target platform:

25	24

26 ./build.py -t chrome build -k adblockpluschrome.pem	25 ./build.py -t chrome build -k adblockpluschrome.pem

27 ./build.py -t safari build -k adblockplussafari.pem	26 ./build.py -t safari build -k adblockplussafari.pem

28	27

29 This will create a build with a name in the form	28 This will create a build with a name in the form

(...skipping 28 matching lines...) Expand all Loading...
58 Running the unit tests	57 Running the unit tests

59 ----------------------	58 ----------------------

60	59

61 To verify your changes you can use the unit test suite located in the _qunit_	60 To verify your changes you can use the unit test suite located in the _qunit_

62 directory of the repository. In order to run the unit tests go to the	61 directory of the repository. In order to run the unit tests go to the

63 extension's Options page, open the JavaScript Console and type in:	62 extension's Options page, open the JavaScript Console and type in:

64	63

65 location.href = "qunit/index.html";	64 location.href = "qunit/index.html";

66	65

67 The unit tests will run automatically once the page loads.	66 The unit tests will run automatically once the page loads.

OLD	NEW