Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code

Side by Side Diff: README.md

Issue 29527808: Noissue - Use meson to build the C++ code (Closed) Base URL: https://hg.adblockplus.org/adblockpluscore/
Patch Set: Pin meson version. Deprecate compile Created Dec. 13, 2017, 5:09 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 | « .hgignore ('k') | compile » ('j') | compile » ('J')
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 Adblock Plus core 1 Adblock Plus core
2 ================= 2 =================
3 3
4 This repository contains the generic Adblock Plus code that's shared between 4 This repository contains the generic Adblock Plus code that's shared between
5 platforms. This repository is not designed to be used directly, but instead to 5 platforms. This repository is not designed to be used directly, but instead to
6 serve as a dependency for `adblockplus`, `adblockpluschrome` and 6 serve as a dependency for `adblockplus`, `adblockpluschrome` and
7 `libadblockplus`. 7 `libadblockplus`.
8 8
9 Compiling C++ code 9 Compiling C++ code
10 ------------------ 10 ------------------
11 11
12 ### Purpose 12 ### Purpose
13 13
14 In order to improve performance and memory usage, some of the code (located 14 In order to improve performance and memory usage, some of the code (located
15 inside the `compiled` directory) is written in C++ and compiled to JavaScript 15 inside the `compiled` directory) is written in C++ and compiled to JavaScript
16 via Empscripten. 16 via Empscripten.
17 17
18 ### Requirements 18 ### Requirements
19 19
20 * [Emscripten 1.37.3](https://github.com/kripken/emscripten) 20 * [Emscripten 1.37.3](https://github.com/kripken/emscripten)
21 * [Python 2.7](https://www.python.org) 21 * [Python 2.7 & 3](https://www.python.org)
Wladimir Palant 2017/12/14 10:57:01 Python 3 is a transitive dependency for Meson, we
hub 2017/12/15 17:44:55 Done.
22 * [meson 0.43.0](https://www.mesonbuild.com)
23 * [ninja](https://www.ninja-build.org)
24
25 Make sure that meson and ninja are in your PATH.
22 26
23 ### Running Emscripten 27 ### Running Emscripten
24 28
25 After installing and configuring Emscripten you can run the following command: 29 After installing and configuring Emscripten you can setup the build
30 with the following commands:
26 31
27 python compile 32 meson build
33
34 By default it will create a debug build. Pass `--buildtype release` to
35 create a release build.
36
37 Then to build just do:
38
39 ninja -C build
40
41 This will regenerate the build files as needed.
28 42
29 This will produce a `lib/compiled.js` exporting the classes defined in C++ code. 43 This will produce a `lib/compiled.js` exporting the classes defined in C++ code.
30 44
31 ### Technical details 45 ### Technical details
32 46
33 Compilation is currently a two-step process. In the bindings generation step, 47 Compilation is currently a two-step process. In the bindings generation step,
34 the source files are compiled into `compiled/bindings.cpp.js` with the 48 the source files are compiled into `compiled/bindings.cpp.js` with the
35 `PRINT_BINDINGS` symbol defined. This application is then executed via Node.js 49 `PRINT_BINDINGS` symbol defined. This application is then executed via Node.js
36 and will print JavaScript wrappers for the C++ classes to 50 and will print JavaScript wrappers for the C++ classes to
37 `compiled/bindings.js` according to definitions within the `EMSCRIPTEN_BINDINGS` 51 `build/bindings.js` according to definitions within the `EMSCRIPTEN_BINDINGS`
38 macro in `compiled/bindings.cpp`. 52 macro in `compiled/bindings.cpp`.
39 53
40 In the actual compilation step the source files are compiled into 54 In the actual compilation step the source files are compiled into
41 `lib/compiled.js` without the `PRINT_BINDINGS` symbol, so that the 55 `lib/compiled.js` without the `PRINT_BINDINGS` symbol, so that the
42 `EMSCRIPTEN_BINDINGS` macro ignores its contents and merely emits some generic 56 `EMSCRIPTEN_BINDINGS` macro ignores its contents and merely emits some generic
43 functions necessary for the JavaScript bindings to work. The previously 57 functions necessary for the JavaScript bindings to work. The previously
44 generated `compiled/bindings.js` file is added to the end of Emscripten output. 58 generated `compiled/bindings.js` file is added to the end of Emscripten output.
45 59
46 The binding generation approach is heavily inspired by 60 The binding generation approach is heavily inspired by
47 [embind](http://kripken.github.io/emscripten-site/docs/porting/connecting_cpp_an d_javascript/embind.html). 61 [embind](http://kripken.github.io/emscripten-site/docs/porting/connecting_cpp_an d_javascript/embind.html).
(...skipping 37 matching lines...) Expand 10 before | Expand all | Expand 10 after
85 Linting 99 Linting
86 ------- 100 -------
87 101
88 You can lint the code using [ESLint](http://eslint.org). 102 You can lint the code using [ESLint](http://eslint.org).
89 103
90 eslint *.js chrome lib test 104 eslint *.js chrome lib test
91 105
92 You will need to set up ESLint and our configuration first, see 106 You will need to set up ESLint and our configuration first, see
93 [eslint-config-eyeo](https://hg.adblockplus.org/codingtools/file/tip/eslint-conf ig-eyeo) 107 [eslint-config-eyeo](https://hg.adblockplus.org/codingtools/file/tip/eslint-conf ig-eyeo)
94 for more information. 108 for more information.
OLDNEW
« no previous file with comments | « .hgignore ('k') | compile » ('j') | compile » ('J')

Powered by Google App Engine
This is Rietveld