Changes

Jump to: navigation, search

Porting to a new device

180 bytes removed, 19:02, 17 February 2018
update "pmbootstrap init" output: we ask for the work folder as first question (bootimg_analyze used in the device step requires a functional work folder), build options have been grouped
$ cd pmbootstrap
$ ./pmbootstrap.py init
Location of the 'work' path. Multiple chroots (native, device arch, device rootfs) will be created in there.
Work path [/home/user/.local/var/pmbootstrap]:
</syntaxhighlight>
<pre>
Target device (either an existing one, or a new one for porting).
Available (3160): asus-flo, asus-grouper, fairphone-fp2, ...
Device [samsung-i9100]: wiki-example
You are about to do a new device port for 'wiki-example'.
* xfce4: (X11) Lightweight GTK+2 desktop (stylus recommended)
User interface [weston]:
Location of the 'work' path. Multiple chroots (native, device arch, device rootfs) will be created in there.Work path [/home/user/.local/var/pmbootstrap]Build options:How many Parallel jobs should run parallel on this machine: 3, when compiling?Jobs [3]ccache per arch:5GRebuild packages, when the last modified timestamp changed, even if the version did not changeChange them? This makes pmbootstrap behave more like 'make'.Timestamp based rebuilds (y/n) [n]:
Additional packages that will be installed to rootfs. Specify them in a comma separated list (e.g.: vim,file) or "none"
Extra packages [none]:

Navigation menu