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.
|
|
|
|
|
|
|
|
|
|
DEVELOPMENT
|
|
|
|
|
===========
|
|
|
|
|
|
|
|
|
|
Development builds can be built and/or run with
|
|
|
|
|
|
|
|
|
|
# cargo build
|
2019-09-21 21:25:21 +03:00
|
|
|
# cargo run
|
2019-07-13 22:47:06 +03:00
|
|
|
|
2019-09-21 21:25:21 +03:00
|
|
|
There is a debug/tracing log feature that can be enabled by using the flag
|
|
|
|
|
`--feature debug-tracing` or in a development profile in Cargo.toml. The logs
|
|
|
|
|
are printed in stderr, thus you can run meli with a redirection (i.e `2> log`)
|
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:
|
|
|
|
|
|
2019-09-21 21:25:21 +03:00
|
|
|
# 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
|
