OLD | NEW |
1 naclports - Ports of open source software to Native Client | 1 naclports - Ports of open source software to Native Client |
2 ========================================================== | 2 ========================================================== |
3 | 3 |
4 naclports is collection of open source libraries and applications that have | 4 naclports is collection of open source libraries and applications that have |
5 been ported to Native Client, along with set to tools for building and | 5 been ported to Native Client, along with set to tools for building and |
6 maintaining them. | 6 maintaining them. |
7 | 7 |
8 Packages can be built from source or prebuilt binaries packages can be | 8 Packages can be built from source or prebuilt binaries packages can be |
9 downloaded from the continuous build system. | 9 downloaded from the continuous build system. |
10 | 10 |
(...skipping 62 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
73 installing: | 73 installing: |
74 | 74 |
75 - zlib1g-dev:i386 | 75 - zlib1g-dev:i386 |
76 - libssl-dev:i386 | 76 - libssl-dev:i386 |
77 | 77 |
78 On older Debian/Ubuntu systems the packages were called: | 78 On older Debian/Ubuntu systems the packages were called: |
79 | 79 |
80 - lib32z1-dev | 80 - lib32z1-dev |
81 - libssl0.9.8:i | 81 - libssl0.9.8:i |
82 | 82 |
83 To run the presubmit checks (or ``make test``) you will also need to have | |
84 the ``coverage`` Python module installed. | |
85 | |
86 | 83 |
87 Building | 84 Building |
88 -------- | 85 -------- |
89 | 86 |
90 Before you can build any of the package you must set the ``NACL_SDK_ROOT`` | 87 Before you can build any of the package you must set the ``NACL_SDK_ROOT`` |
91 environment variable to top directory of a version of the Native Client SDK | 88 environment variable to top directory of a version of the Native Client SDK |
92 (the directory containing toolchain/). This path should be absolute. | 89 (the directory containing toolchain/). This path should be absolute. |
93 | 90 |
94 The top level Makefile can be used as a quick way to build one or more | 91 The top level Makefile can be used as a quick way to build one or more |
95 packages. For example, ``make libvorbis`` will build ``libvorbis`` and | 92 packages. For example, ``make libvorbis`` will build ``libvorbis`` and |
(...skipping 137 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
233 1. Directly modify the sources in ``out/build/PKG_NAME``. | 230 1. Directly modify the sources in ``out/build/PKG_NAME``. |
234 2. Build the package and verify the changes. | 231 2. Build the package and verify the changes. |
235 3. Use ``git diff upstream.. > ../path/to/nacl.patch`` to regenerate | 232 3. Use ``git diff upstream.. > ../path/to/nacl.patch`` to regenerate |
236 the patch file. | 233 the patch file. |
237 | 234 |
238 Whenever the upstream archive or patch file changes and you try to build the | 235 Whenever the upstream archive or patch file changes and you try to build the |
239 package you will be prompted to remove the existing repository and start a new | 236 package you will be prompted to remove the existing repository and start a new |
240 one. This is to avoid deleting a repository that might have unsaved changed. | 237 one. This is to avoid deleting a repository that might have unsaved changed. |
241 | 238 |
242 Happy porting! | 239 Happy porting! |
OLD | NEW |