Skip to content

Commit

Permalink
Update some of the README information.
Browse files Browse the repository at this point in the history
* Necessary disk space for build: my build needs almost 200G. Mention this as a warning.
* Do not use anything like "FP3.xml" for the local manifest file. The build system, especially
  vendor/lineage/build/tools/roomservice.py
  use a hardcoded file named 'roomservice.xml'. Not observing this will result in the warning message
  'Trying dependencies-only mode on a non-existing device tree?'
  and maybe some further errors since our local repos would not update correctly.

Change-Id: I567b776a6331a4b6adbff89f0b526c2b40b9a845
  • Loading branch information
dk1978 committed Jul 11, 2020
1 parent dafc4c2 commit e987567
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ Kernel sources are here in the lineage-16.0 branch:


### How to build
* Follow the first steps for setting up the LineageOS build system as described e.g. [here](https://wiki.lineageos.org/devices/river/build).
* Follow the first steps for setting up the LineageOS build system as described e.g. [here](https://wiki.lineageos.org/devices/river/build). Be aware that a complete build can occupy up to 200G of disk space!
* Before downloading the source code using repo sync, create a local manifest file in `.repo/local_manifests`. From the
top of the source tree this command can be used:
```sh
Expand All @@ -80,7 +80,7 @@ cat <<EOF > .repo/local_manifests/roomservice.xml
</manifest>
EOF
```
The file name doesn't matter, e.g. also `FP3.xml` works. This is a temporary hack while we are working outside of the LineageOS repositories. Note that we are pulling in proprietary blobs from a repository, see the section below for how these can be extracted from a firmware image or running device.
This is a temporary hack while we are working outside of the LineageOS repositories. Note that we are pulling in proprietary blobs from a repository, see the section below for how these can be extracted from a firmware image or running device.

* Do `repo sync -c` to download all needed project repositories.
* Then do
Expand All @@ -100,7 +100,7 @@ mkdir cache keys lineage logs manifests zips

Create the local manifest file in manifest directory:
```sh
cat <<EOF > manifests/FP3.xml
cat <<EOF > manifests/roomservice.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="WeAreFairphone/android_device_fairphone_FP3" path="device/fairphone/FP3" revision="lineage-16.0" remote="github" />
Expand Down

0 comments on commit e987567

Please sign in to comment.