wasm-demo/README

105 lines
2.9 KiB
Plaintext
Raw Normal View History

2019-09-22 22:51:34 +03:00
__
__/ \__
/ \__/ \__ .
\__/ \__/ \ , _ , _ ___ │ '
/ \__ \__/ │' `│ `┒ .' ` │ │
\__/ \__/ \ │ │ │ |────' │ │
\__/ \__/ │ / `.___, /\__ /
\__/
,-.
\_/
terminal mail user agent {|||)<
/ \
`-'
DOCUMENTATION
=============
After installing meli, see meli(1) and meli.conf(5) for documentation.
BUILDING
========
meli requires rust 1.34 and rust's package manager, Cargo. Information on how
to get it on your system can be found here:
https://doc.rust-lang.org/cargo/getting-started/installation.html
With Cargo available, the project can be built with
# make
The resulting binary will then be found under target/release/meli
Run:
# make install
to install the binary and man pages. This requires root, so I suggest you override the default paths and install it in your $HOME:
# make PREFIX=$HOME/.local install
See meli(1) and meli.conf(5) for documentation.
You can build and run meli with one command:
# cargo run --release
2019-07-13 22:47:06 +03:00
While the project is in early development, meli will only be developed for the
linux kernel and respected linux distributions. Support for more UNIX-like OSes
is on the roadmap.
BUILDING IN DEBIAN
==================
Building with Debian's packaged cargo might require the installation of these
two packages: librust-openssl-sys-dev and librust-libdbus-sys-dev
BUILDING WITH NOTMUCH
=====================
To use the optional notmuch backend feature, you must have libnotmuch installed in your system. In Debian-like systems, install the "libnotmuch" package.
To build with notmuch support, prepend the environment variable "MELI_FEATURES='melib/notmuch_backend'" to your make invocation:
# MELI_FEATURES="melib/notmuch_backend" make
or if building directly with cargo, use the flag '--features="melib/notmuch_backend"'.
2019-07-13 22:47:06 +03:00
DEVELOPMENT
===========
Development builds can be built and/or run with
# cargo build
# cargo run
2019-07-13 22:47:06 +03:00
There is a debug/tracing log feature that can be enabled by using the flag
`--feature debug-tracing` after uncommenting the features in `Cargo.toml`. The logs
are printed in stderr, thus you can run meli with a redirection (i.e `2> log`)
Code style follows the default rustfmt profile.
2019-07-13 22:47:06 +03:00
CONFIG
2018-08-04 20:30:21 +03:00
======
2019-07-13 22:47:06 +03:00
meli by default looks for a configuration file in this location:
2018-08-04 20:30:21 +03:00
# $XDG_CONFIG_HOME/meli/config
2019-07-13 22:47:06 +03:00
You can run meli with arbitrary configuration files by setting the MELI_CONFIG
environment variable to their locations, ie:
# MELI_CONFIG=./test_config cargo run
2019-07-13 22:47:06 +03:00
TESTING
2018-08-14 00:13:08 +03:00
=======
2019-07-13 22:47:06 +03:00
How to run specific tests:
2018-08-14 00:13:08 +03:00
# cargo test -p {melib, ui, meli} (-- --nocapture) (--test test_name)
2019-07-13 22:47:06 +03:00
PROFILING
=========
2018-08-04 20:30:21 +03:00
# perf record -g target/debug/bin
# perf script | stackcollapse-perf | rust-unmangle | flamegraph > perf.svg