| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
| |
- rvi_install & rvi_ctl adapted so they can be run from different directories
- ensure that RVI_LOGDIR is respected consistently
- RVI_RUNDIR allows for specifying where the boot scripts are stored
- bt apps excluded by default, can be put back in through config if needed
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The original rebar.config.script uses erland:system_info(system_architecture)
to obtain the machine triplet e.g x86_64-redhat-linux-gnu. This does not work
in a cross environment where rebar runs inside a native Erlang runtime. The
rebar script now tries to detect if it runs in a cross environment by checking
the envrionment variable CXX. If it's set that typically indicates that a
cross compiler is used (but even if not it won't hurt). It then determines the
machine triplet from the cross compiler as well as the sysroot.
Signed-off-by: Rudolf J Streif <rudolf.streif@gmail.com>
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
- No signatures on messages (dlink_tls)
- dlink_bt wasn't actually tested (test case passed erroneously)
- added proto_msgpack component
- fixed sneaky bug in 'setup'
|
| |
|
|
|
|
|
|
|
|
| |
* Introduced high-level logging (rvi_log)
* Upgraded to new lager version, customized debug output
* Thread rvi_log IDs between nodes and components
* Introduce simplified protocol for dlink_tls
* Use msgpack encoding for dlink_tls
* dlink_bt can use TCP instead of Bluetooth for testing purposes
* Bug fixes and additions to the test suite
|
| | |
|
| |
|
|
|
|
|
|
| |
- Authorization works just like for dlink_tcp
- After authorization, the TCP session is upgraded to TLS
- Currently, hard-coded use of OTP's example certs and keys
- Test suite installs a tls client and tls backend, but doesn't start them
- Manually tested that authorization and service announcement work
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| |
|
