Hash :
9534a8f7
Author :
Date :
2015-07-13T17:05:31
Fix more links and incorrect newlines in markdown files. Change-Id: I3c96b0408d80be0f47c968566301637f49fe98c6 Reviewed-on: https://chromium-review.googlesource.com/285224 Reviewed-by: Geoff Lang <geofflang@chromium.org> Tested-by: Geoff Lang <geofflang@chromium.org>
ANGLE is normally built on Windows but parts of it are cross platform including the shader validator and translator. These parts can be built and tested inside a Chromium checkout.
Steps:
cd src/third_party/angle
gclient config --name . --unmanaged https://chromium.googlesource.com/angle/angle.git
gclient sync
git checkout master
cd src/third_party/angle
GYP_GENERATORS=ninja gclient runhooks
cd src/third_party/angle
ninja -j 10 -k1 -C out/Debug
cd src/third_party/angle
ninja -j 10 -k1 -C out/Debug angle_compiler_tests
cd src/third_party/angle
./out/Debug/angle_compiler_tests
If you’re actively developing within ANGLE in your Chromium workspace you will want to work with top of tree ANGLE. To do this do the following:
.gclient solutions = [
{
# ...
u'custom_deps':
{
"src/third_party/angle": None,
},
},
]
You then have full control over your ANGLE workspace and are responsible for running all git commands (pull, rebase, etc.) for managing your branches.
If you decide you need to go back to the DEPS version of ANGLE:
src/third_party/angle line in your custom_deps. gclient sync your Chromium workspace.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74
# How to build ANGLE in Chromium for dev
## Introduction
ANGLE is normally built on Windows but parts of it are cross platform including the shader validator and translator. These parts can be built and tested inside a Chromium checkout.
## Details
Steps:
* Checkout and build [Chromium](http://dev.chromium.org/Home).
* To setup run these commands (note similarity to [DevSetup](DevSetup.md)):
```bash
cd src/third_party/angle
gclient config --name . --unmanaged https://chromium.googlesource.com/angle/angle.git
gclient sync
git checkout master
```
* To make the build files run these commands
```bash
cd src/third_party/angle
GYP_GENERATORS=ninja gclient runhooks
```
* To build
```bash
cd src/third_party/angle
ninja -j 10 -k1 -C out/Debug
```
* To build a specific target add the target at the end:
```bash
cd src/third_party/angle
ninja -j 10 -k1 -C out/Debug angle_compiler_tests
```
* To run
```bash
cd src/third_party/angle
./out/Debug/angle_compiler_tests
```
## Working with Top of Tree ANGLE in Chromium
If you're actively developing within ANGLE in your Chromium workspace you will want to work with top of tree ANGLE. To do this do the following:
* Ignore ANGLE in your `.gclient`
```python
solutions = [
{
# ...
u'custom_deps':
{
"src/third_party/angle": None,
},
},
]
```
You then have full control over your ANGLE workspace and are responsible for running all git commands (pull, rebase, etc.) for managing your branches.
If you decide you need to go back to the DEPS version of ANGLE:
* Comment out the `src/third_party/angle` line in your `custom_deps`.
* Go into your ANGLE workspace and switch back to the master branch (ensure there are no modified or new files).
* `gclient sync` your Chromium workspace.