Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(336)

Side by Side Diff: docs/accessibility/brltty.md

Issue 2701603002: Update accessibility documentation. (Closed)
Patch Set: Created 3 years, 10 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « docs/accessibility.md ('k') | docs/accessibility/chromevox.md » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
(Empty)
1 # BRLTTY in Chrome OS
2
3 Chrome OS uses the open-source [BRLTTY](http://mielke.cc/brltty/)
4 library to provide support for refreshable braille displays.
5
6 We typically ship with a stable release build of BRLTTY plus some
7 cherry-picked patches.
8
9 ## Updating BRLTTY or adding a patch
10
11 First, follow the public
12 [Chromium OS Developer Guide](http://www.chromium.org/chromium-os/developer-guid e) to check out the source.
13 At a minimum you'll need to create a chroot.
14 You do not need to build everything from source.
15 You do need to start the devserver.
16
17 Next, flash your device to a very recent test build. Internally at Google
18 you can do this with the following command when the dev server is running,
19 where CHROMEBOOK_IP_ADDRESS is the IP address of your Chromebook already
20 in developer mode, and $BOARD is your Chromebook's board name.
21
22 ```cros flash ssh://CHROMEBOOK_IP_ADDRESS xbuddy://remote/$BOARD/latest-dev/test ```
23
24 The BRLTTY files can be found in this directory:
25
26 ```third_party/chromiumos-overlay/app-accessibility/brltty```
27
28 The first thing you'll need to do is edit the ebuild symlink to change the
29 revision number. The real file is something like brltty-5.4.ebuild,
30 but the revision will be something like brltty-5.4-r5.ebuild. You'll need
31 to increment it.
32
33 To increment it from r5 to r6, you'd do something like this:
34
35 ```
36 rm brltty-5.4-r5.ebuild
37 ln -s brltty-5.4.ebuild brltty-5.4-r6.ebuild
38 git add brltty-5.4-r6.ebuild
39 ```
40
41 The changes we make are all patches against a stable release of brltty.
42 To add a new patch, put it in the files/ directory and reference it in
43 brltty.bashrc
44
45 Once you're done adding patches or making other changes, flash it to your
46 device like this:
47
48 ```
49 emerge-$BOARD brltty
50 cros deploy CHROMEBOOK_IP_ADDRESS brltty
51 ```
52
53 After that, reboot your Chromebook and verify that brltty works.
54
55 To upload a change, use repo, something like this:
56
57 ```
58 repo start <branch_name> .
59 git commit -a
60 BUG=chromium:12345
61 TEST=Write what you tested here
62 repo upload .
63 ```
64
65 Note that you shouldn't need to run cros_workon.
OLDNEW
« no previous file with comments | « docs/accessibility.md ('k') | docs/accessibility/chromevox.md » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698