monitoranna.blogg.se - Ubuntu chromium os

#UBUNTU CHROMIUM OS CODE#

The guide is organized linearly, so that developers who are new to ChromiumOS can follow the tasks in sequence. This guide describes the common tasks required to develop ChromiumOS. That includes new developers who are interested in the project and who simply want to browse through the ChromiumOS code, as well as developers who have been working on ChromiumOS for a long time. The target audience of this guide is anyone who wants to obtain, build, or contribute to ChromiumOS.

Creating a recovery image that has been modified for test.

Creating a normal image that has been modified for test.

Set up SSH connection between chroot and DUT.

I lost my developer tools on the stateful partition, can I get them back?.

Automated remote debugging using gdb-$ script.

Debugging both x86 and non-x86 binaries on your workstation.

Making changes to the Chromium web browser on ChromiumOS.

Making changes to the way that the chroot is constructed.

Adding small patches to existing packages.

Making changes to non-cros-workon-able packages.

Clean up after you're done with your changes.

#UBUNTU CHROMIUM OS CODE#

Upload your changes and get a code review.Find out which ebuilds map to which directories.

Making changes to packages whose source code is checked into ChromiumOS git repositories.Installing your ChromiumOS image to your hard disk.Getting to a command prompt on ChromiumOS.Authenticate for remote Bazel caching with RBE, if applicable.Make sure you are authorized to access Google Storage (GS) buckets.Verify that your default file permissions (umask) setting is correct.Double-check that you are running a 64-bit architecture.