development / ports / opt-arm.git / blame
| Commit | Line | Data |
|---|---|---|
| 0826c9bd JB |
1 | |
| 2 | README for chromium | |
| 3 | ||
| 4 | ||
| 5 | NOTES | |
| 6 | ||
| 7 | Some features of Chromium > 23.x.x.x use Google APIs, and to access those APIs | |
| 8 | either an API Key or a set of OAuth 2.0 tokens is required. You can specify | |
| 9 | the API keys to use either when you build Chromium, or at runtime using | |
| 10 | environment variables. | |
| 11 | After build chromium you will have a binary without API keys baked in, so | |
| 12 | instead you should provide them at runtime. | |
| 13 | ||
| 14 | To read more about API keys: | |
| 15 | http://www.chromium.org/developers/how-tos/api-keys | |
| 16 | ||
| 17 | ||
| 18 | POSTINSTALLATION | |
| 19 | ||
| 20 | If you can't run chromium and you got a message like this: | |
| 21 | ||
| 22 | $ chromium | |
| 23 | [1410:1410:1506374616:FATAL:platform_font_gtk.cc(329)] Check failed: typeface. | |
| 24 | Could not find any font: Fixed, sans | |
| 25 | Aborted | |
| 26 | ||
| 27 | you could solve this by installing for example xorg/xorg-font-dejavu-ttf. |