Chromium Code Reviews Chromium Code Reviews
Issue 710193003:
Reduce the number of times we build a host copy of python. (Closed)
Base URL: https://chromium.googlesource.com/external/naclports.git@master| 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 51 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 62 | 62 |
| 63 To ensure you have all required packages you can run the | 63 To ensure you have all required packages you can run the |
| 64 install-build-deps.sh from the chromium repo. | 64 install-build-deps.sh from the chromium repo. |
| 65 | 65 |
| 66 On Mac OS X you can use homebrew to install these using the following command:: | 66 On Mac OS X you can use homebrew to install these using the following command:: |
| 67 | 67 |
| 68 brew install autoconf automake cmake gettext libtool pkg-config | 68 brew install autoconf automake cmake gettext libtool pkg-config |
| 69 | 69 |
| 70 The build system for some of the native Python modules relies on a 32-bit | 70 The build system for some of the native Python modules relies on a 32-bit |
| 71 host build of Python itself, which in turn relies on the development version | 71 host build of Python itself, which in turn relies on the development version |
| 72 of zlib being available. On 64-bit Ubuntu/Precise this means installing the | 72 of zlib and libssl being available. On 64-bit Ubuntu/Trust this means |
|
binji
2014/11/10 22:21:30
Trusty
| |
| 73 following package: ``lib32z1-dev``. | 73 installing: |
| 74 | |
| 75 - zlib1g-dev:i386 | |
| 76 - libssl-dev:i386 | |
| 77 | |
| 78 On older Debian/Ubuntu systems the packages were called: | |
| 79 | |
| 80 - lib32z1-dev | |
| 81 - libssl0.9.8:i | |
|
binji
2014/11/10 22:21:30
i386?
| |
| 74 | 82 |
| 75 To run the presubmit checks (or ``make test``) you will also need to have | 83 To run the presubmit checks (or ``make test``) you will also need to have |
| 76 python coverage module installed. | 84 the ``coverage`` Python module installed. |
| 85 | |
| 77 | 86 |
| 78 Building | 87 Building |
| 79 -------- | 88 -------- |
| 80 | 89 |
| 81 Before you can build any of the package you must set the ``NACL_SDK_ROOT`` | 90 Before you can build any of the package you must set the ``NACL_SDK_ROOT`` |
| 82 environment variable to top directory of a version of the Native Client SDK | 91 environment variable to top directory of a version of the Native Client SDK |
| 83 (the directory containing toolchain/). This path should be absolute. | 92 (the directory containing toolchain/). This path should be absolute. |
| 84 | 93 |
| 85 The top level Makefile can be used as a quick way to build one or more | 94 The top level Makefile can be used as a quick way to build one or more |
| 86 packages. For example, ``make libvorbis`` will build ``libvorbis`` and | 95 packages. For example, ``make libvorbis`` will build ``libvorbis`` and |
| (...skipping 137 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 224 1. Directly modify the sources in ``out/build/PKG_NAME``. | 233 1. Directly modify the sources in ``out/build/PKG_NAME``. |
| 225 2. Build the package and verify the changes. | 234 2. Build the package and verify the changes. |
| 226 3. Use ``git diff upstream.. > ../path/to/nacl.patch`` to regenerate | 235 3. Use ``git diff upstream.. > ../path/to/nacl.patch`` to regenerate |
| 227 the patch file. | 236 the patch file. |
| 228 | 237 |
| 229 Whenever the upstream archive or patch file changes and you try to build the | 238 Whenever the upstream archive or patch file changes and you try to build the |
| 230 package you will be prompted to remove the existing repository and start a new | 239 package you will be prompted to remove the existing repository and start a new |
| 231 one. This is to avoid deleting a repository that might have unsaved changed. | 240 one. This is to avoid deleting a repository that might have unsaved changed. |
| 232 | 241 |
| 233 Happy porting! | 242 Happy porting! |
| OLD | NEW |
