mirror of
https://gitlab.gnome.org/GNOME/calls.git
synced 2024-12-04 20:07:36 +00:00
Update README: Explain how to start calls without installing
Additionally get rid of the /usr/local/stow/calls-git prefix.
This commit is contained in:
parent
04b81dd664
commit
2ae79ea06f
1 changed files with 25 additions and 10 deletions
35
README.md
35
README.md
|
@ -19,10 +19,20 @@ If you are running a Debian based distribution, you can easily install all those
|
|||
We use the meson and thereby Ninja. The quickest way to get going is
|
||||
to do the following:
|
||||
|
||||
meson -Dprefix=/usr/local/stow/calls-git ../calls-build
|
||||
ninja -C ../calls-build
|
||||
ninja -C ../calls-build install
|
||||
meson . _build
|
||||
ninja -C _build
|
||||
ninja -C _build install
|
||||
|
||||
If you don't want to pollute your filesystem please be aware, that you can also
|
||||
use `--prefix=~/install`.
|
||||
|
||||
### Build the documentation
|
||||
If you want to build the documentation you have to configure the meson project
|
||||
with `-Ggtk_doc=true`
|
||||
|
||||
meson . _build -Dgtk_doc=true
|
||||
ninja -C _build
|
||||
ninja -C _build calls-doc
|
||||
|
||||
## Running
|
||||
Calls has a variety of backends. The default backend is "mm", which
|
||||
|
@ -31,18 +41,23 @@ command-line option. For example, to run with the dummy backend and
|
|||
some useful debugging output:
|
||||
|
||||
export G_MESSAGES_DEBUG=all
|
||||
/usr/local/stow/calls-git/bin/calls -p dummy
|
||||
/usr/bin/gnome-calls -p dummy
|
||||
|
||||
If using ModemManager, Calls will wait for ModemManager to appear on
|
||||
D-Bus and then wait for usable modems to appear. The UI will be
|
||||
inactive and display a status message until a usable modem appears.
|
||||
|
||||
When running from the source tree you can use `CALLS_PLUGIN_DIR` environment
|
||||
varible to specify the directroy from where plugins are loaded. To e.g. load
|
||||
the dummy plugin from the source tree:
|
||||
### Running from the build directory
|
||||
You can run calls without having to install it by executing the run script in
|
||||
the build folder, i.e. `_build/run`
|
||||
|
||||
When running from the build tree you can use `CALLS_PLUGIN_DIR` environment
|
||||
varible to specify the directroy from where plugins are loaded. To e.g. load
|
||||
the dummy plugin from the build tree:
|
||||
|
||||
export CALLS_PLUGIN_DIR=_build/plugins/
|
||||
_build/run -p dummy
|
||||
|
||||
export CALLS_PLUGIN_DIR=_build/plugins/dummy/
|
||||
_build/src/gnome-calls -p dummy
|
||||
|
||||
### oFono
|
||||
There is also an oFono backend, "ofono". This was the first backend
|
||||
|
@ -65,7 +80,7 @@ useful to bring up a modem to a suitable state. For example:
|
|||
|
||||
Then run Calls:
|
||||
|
||||
/usr/local/stow/calls-git/bin/calls -p ofono
|
||||
/usr/bin/gnome-calls -p ofono
|
||||
|
||||
|
||||
#### Phonesim
|
||||
|
|
Loading…
Reference in a new issue