Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found

Target

Select target project
  • Librem5/developer.puri.sm
  • heather.ellsworth/developer.puri.sm
  • guido.gunther/developer.puri.sm
  • nihaal/developer.puri.sm
  • albfan/developer.puri.sm
  • adrien.plazas/developer.puri.sm
  • dcushman/developer.puri.sm
  • kill_all_humans/developer.puri.sm
  • blendergeek/developer.puri.sm
  • jjardon/developer.puri.sm
  • david.boddie/developer.puri.sm
  • dorota.czaplejewicz/developer.puri.sm
  • bob.ham/developer.puri.sm
  • eric.kuzmenko/developer.puri.sm
  • warmcat/developer.puri.sm
  • mike7b4/developer.puri.sm
  • louib/developer.puri.sm
  • mijiturka/developer.puri.sm
  • MJochim/developer.puri.sm
  • craftyguy/developer.puri.sm
  • johkra/developer.puri.sm
  • pan/developer.puri.sm
  • cjp256/developer.puri.sm
  • kortschak/developer.puri.sm
  • neiljerram/developer.puri.sm
  • nah_omy/developer.puri.sm
  • Hofer-Julian/developer.puri.sm
  • Kpurism/developer.puri.sm
  • docbibi/developer.puri.sm
  • joao.azevedo/developer.puri.sm
  • spacemanspiffy/developer.puri.sm
  • dct/developer.puri.sm
  • sebastian.krzyszkowiak/developer.puri.sm
  • Rich_Morin/developer.puri.sm
  • julian.sparber/developer.puri.sm
  • simonhdickson/developer.puri.sm
  • david.hamner/developer.puri.sm
  • Pure_Supporter/developer.puri.sm
  • evangelos.tzaras/developer.puri.sm
  • petrisch/developer.puri.sm
  • bradley.taunt/developer.puri.sm
  • francois.techene/developer.puri.sm
  • janvlug/developer.puri.sm
  • lio56/developer.puri.sm
  • irvinewade/developer.puri.sm
45 results
Show changes
Commits on Source (11)
Showing
with 20 additions and 18 deletions
...@@ -38,6 +38,6 @@ publish: ...@@ -38,6 +38,6 @@ publish:
- touch ~/.ssh/id_rsa - touch ~/.ssh/id_rsa
- chmod 0600 ~/.ssh/id_rsa - chmod 0600 ~/.ssh/id_rsa
- echo "$SSH_KEY" >> ~/.ssh/id_rsa - echo "$SSH_KEY" >> ~/.ssh/id_rsa
- rsync -av -i --stats -e "ssh -l $SSH_USER -p $SSH_PORT" --delete-after _build/html/ $RSYNC_TARGET - rsync -av -i --stats -e "ssh -l $SSH_USER -i ~/.ssh/id_rsa -p $SSH_PORT" _build/html/ "$RSYNC_TARGET"
only: only:
- master - master
Subproject commit 82f5ec30d1cdd5e074d72892aa0beb045b332430 Subproject commit bf4407daec7e4ee89993593af3d4d67763ac95d3
Subproject commit 11d12ca7f68d7afbbc3cbc4e66b9221f2af0f15d Subproject commit 49244a3274fd0bad87cfd6dc5c2bb6eb4355c492
Subproject commit d10a4fbfc77706ceaa75d3dfba349a643bb3ce5d Subproject commit e2292105334161d9d7049e7d05941ab11730f6e2
Subproject commit 0cf651ad90d6c726491eecd6476b9753fe22b0a1 Subproject commit e2675409026b334e39616a581e56dfdc706651b4
...@@ -78,7 +78,7 @@ to install the runtime and SDK that the application depends on. These are the ...@@ -78,7 +78,7 @@ to install the runtime and SDK that the application depends on. These are the
same as those mentioned in :ref:`flatpak_setup_gnome` except that we need the same as those mentioned in :ref:`flatpak_setup_gnome` except that we need the
ones for the aarch64 architecture:: ones for the aarch64 architecture::
flatpak --user install flathub org.gnome.Platform/aarch64/3.30 org.gnome.Sdk/aarch64/3.30 flatpak --user install flathub org.gnome.Platform/aarch64/3.32 org.gnome.Sdk/aarch64/3.32
After installing these, build the application with ``flatpak-builder``: After installing these, build the application with ``flatpak-builder``:
......
...@@ -16,7 +16,7 @@ development system:: ...@@ -16,7 +16,7 @@ development system::
purism@pureos:~$ sudo apt-get install flatpak flatpak-builder purism@pureos:~$ sudo apt-get install flatpak flatpak-builder
purism@pureos:~$ flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo purism@pureos:~$ flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
purism@pureos:~$ flatpak install flathub org.gnome.Platform//3.30 purism@pureos:~$ flatpak install flathub org.gnome.Platform//3.32
You will also need to install a version of the `qemu`_ emulator that can be You will also need to install a version of the `qemu`_ emulator that can be
used to assist with cross-compilation. This is described in used to assist with cross-compilation. This is described in
......
...@@ -8,7 +8,7 @@ This guide aims to show developers and designers how to use the components provi ...@@ -8,7 +8,7 @@ This guide aims to show developers and designers how to use the components provi
.. contents:: .. contents::
:local: :local:
This guide assumes that you are familiar with the basics of GTK application development. It also assumes you are using GTK 3.30 or newer and libhandy 0.0.9 or newer as these versions have improved support for adaptive apps over previous versions. This guide assumes that you are familiar with the basics of GTK application development. It also assumes you are using GTK 3.32 or newer and libhandy 0.0.10 or newer as these versions have improved support for adaptive apps over previous versions.
Introduction Introduction
------------ ------------
......
Subproject commit c21d2ebf1c7cc6664a0edc3b4042d030e2697022 Subproject commit 1df3897970df76a4044d2341154f75df82d751ed
Subproject commit 17e514397e3f0f75685215973ada9d2430327e05 Subproject commit 91f0af57060e80951ea105cedbec227caf9a4481
Subproject commit 996673e8ef3c9fde85ae30a472f92afdd0b2a460 Subproject commit 6f6760890d793fd77aaf4670aae763793c89ae25
Subproject commit 5a1d82273ecaa64713662f2e3bb777c3510e859f Subproject commit 83567d9d54d15ffc05932e9af84c7fd8e0d2878c
Subproject commit a05dfd9ae326f8f0bdd518c33d7492bb3d3085da Subproject commit 8840af880d54424fe9684e7a9780cebd70d865cb
...@@ -85,7 +85,7 @@ to install the runtime and SDK that the application depends on. These are the ...@@ -85,7 +85,7 @@ to install the runtime and SDK that the application depends on. These are the
same as those mentioned in :ref:`flatpak_setup_gnome` except that we need the same as those mentioned in :ref:`flatpak_setup_gnome` except that we need the
ones for the aarch64 architecture:: ones for the aarch64 architecture::
flatpak --user install flathub org.gnome.Platform/aarch64/3.30 org.gnome.Sdk/aarch64/3.30 flatpak --user install flathub org.gnome.Platform/aarch64/3.32 org.gnome.Sdk/aarch64/3.32
After installing these, build the application with ``flatpak-builder``: After installing these, build the application with ``flatpak-builder``:
......
...@@ -18,7 +18,7 @@ to install the runtime and SDK that the application depends on. These are the ...@@ -18,7 +18,7 @@ to install the runtime and SDK that the application depends on. These are the
same as those mentioned in :ref:`flatpak_setup_gnome` except that we need the same as those mentioned in :ref:`flatpak_setup_gnome` except that we need the
ones for the aarch64 architecture:: ones for the aarch64 architecture::
flatpak --user install flathub org.gnome.Platform/aarch64/3.30 org.gnome.Sdk/aarch64/3.30 flatpak --user install flathub org.gnome.Platform/aarch64/3.32 org.gnome.Sdk/aarch64/3.32
After installing these, build the application with ``flatpak-builder``. For After installing these, build the application with ``flatpak-builder``. For
example, here is how to build the |app-name| application from the |app-dir| example, here is how to build the |app-name| application from the |app-dir|
......
...@@ -13,7 +13,9 @@ some time due to a lack of entropy (see `linux-emcraft issue 2`_ for details). ...@@ -13,7 +13,9 @@ some time due to a lack of entropy (see `linux-emcraft issue 2`_ for details).
Setting Up and Testing Setting Up and Testing
---------------------- ----------------------
Log in to the board using one of the network connections (Wi-Fi or Ethernet). Log in to the board using one of the network connections (Wi-Fi or Ethernet) as
the user ``purism`` using the default password ``123456``.
Install the ``xauth`` package to enable X11 authorization. X11 forwarding is Install the ``xauth`` package to enable X11 authorization. X11 forwarding is
already enabled by default in the ``sshd`` configuration. already enabled by default in the ``sshd`` configuration.
...@@ -73,8 +75,8 @@ Then simply run Phosh with this command:: ...@@ -73,8 +75,8 @@ Then simply run Phosh with this command::
The lock screen should appear in the Xephyr window. Unlock the screen by The lock screen should appear in the Xephyr window. Unlock the screen by
clicking and dragging upwards or by pressing the space bar, then enter the clicking and dragging upwards or by pressing the space bar, then enter the
``purism`` user's password (123456) to access the shell, either by clicking on ``purism`` user's default password ``123456`` to access the shell, either by
the buttons or by pressing the number keys on the keyboard. clicking on the buttons or by pressing the number keys on the keyboard.
.. figure:: ../images/ssh-x11-phosh-pin-entry.png .. figure:: ../images/ssh-x11-phosh-pin-entry.png
:scale: 50% :scale: 50%
......