2017-09-16 16:27:33 +00:00
|
|
|
__
|
|
|
|
__/ \__
|
|
|
|
/ \__/ \__ .
|
2017-09-28 15:06:35 +00:00
|
|
|
\__/ \__/ \ , _ , _ ___ │ '
|
|
|
|
/ \__ \__/ │' `│ `┒ .' ` │ │
|
|
|
|
\__/ \__/ \ │ │ │ |────' │ │
|
|
|
|
\__/ \__/ │ / `.___, /\__ /
|
2019-06-10 19:15:42 +00:00
|
|
|
\__/
|
2019-07-04 04:38:25 +00:00
|
|
|
,-.
|
|
|
|
\_/
|
2019-06-10 19:15:42 +00:00
|
|
|
terminal mail user agent {|||)<
|
|
|
|
/ \
|
|
|
|
`-'
|
2019-07-04 04:38:25 +00:00
|
|
|
|
2019-07-13 19:47:06 +00:00
|
|
|
BUILDING
|
|
|
|
========
|
2019-07-04 04:38:25 +00:00
|
|
|
|
2019-07-13 19:47:06 +00:00
|
|
|
meli requires rust 1.34 and rust's package manager, Cargo. Information on how
|
|
|
|
to get it on your system can be found here:
|
2019-07-04 04:38:25 +00:00
|
|
|
|
2019-07-13 19:47:06 +00:00
|
|
|
https://doc.rust-lang.org/cargo/getting-started/installation.html
|
|
|
|
|
|
|
|
With Cargo available, the project can be built with
|
|
|
|
|
|
|
|
# cargo build --release
|
|
|
|
|
|
|
|
The resulting binary will then be found under target/release/meli
|
|
|
|
|
|
|
|
You can build and run meli with one command:
|
|
|
|
|
|
|
|
# cargo run --release
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
DEVELOPMENT
|
|
|
|
===========
|
|
|
|
|
|
|
|
Development builds can be built and/or run with
|
|
|
|
|
|
|
|
# cargo build
|
|
|
|
# cargo run 2> debug.log
|
|
|
|
|
|
|
|
The debug logs can be disabled by setting debug-assertions to false in the
|
|
|
|
development profile in Cargo.toml. In the future debug logs will be a feature.
|
|
|
|
|
|
|
|
CONFIG
|
2018-08-04 17:30:21 +00:00
|
|
|
======
|
|
|
|
|
2019-07-13 19:47:06 +00:00
|
|
|
meli by default looks for a configuration file in this location:
|
2018-08-04 17:30:21 +00:00
|
|
|
# $XDG_CONFIG_HOME/meli/config
|
|
|
|
|
2019-07-13 19:47:06 +00: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 2> debug.log
|
|
|
|
|
|
|
|
TESTING
|
2018-08-13 21:13:08 +00:00
|
|
|
=======
|
|
|
|
|
2019-07-13 19:47:06 +00:00
|
|
|
How to run specific tests:
|
|
|
|
|
2018-08-13 21:13:08 +00:00
|
|
|
# cargo test -p {melib, ui, meli} (-- --nocapture) (--test test_name)
|
|
|
|
|
2019-07-13 19:47:06 +00:00
|
|
|
PROFILING
|
|
|
|
=========
|
2018-08-04 17:30:21 +00:00
|
|
|
|
|
|
|
# perf record -g target/debug/bin
|
|
|
|
# perf script | stackcollapse-perf | rust-unmangle | flamegraph > perf.svg
|