-# OpenXC Message Format Specification
+# CAN signaling binder
-There are two valid message types - single valued and evented.
+CAN bus binder, based upon OpenXC vi-firmware project.
-There may not be a 1:1 relationship between input and output signals - i.e. raw
-engine timing CAN signals may be summarized in an "engine performance" metric on
-the abstract side of the interface.
+Full document can be found under `docs` directory.
-## Single Valued
+# Fast build procedure
-The expected format of a single valued message is:
+Just use autobuild script:
-{% highlight javascript %}
-{"name": "steering_wheel_angle", "value": 45}
-{% endhighlight %}
+```bash
+./conf.d/autobuild/agl/autobuild build
+./conf.d/autobuild/agl/autobuild package
+```
-## Evented
+This will build both projects under build directory for each of them with default configuration.
-The expected format of an event message is:
+# Generate documentation
-{% highlight javascript %}
-{"name": "button_event", "value": "up", "event": "pressed"}
-{% endhighlight %}
+## Prerequisites
-This format is good for something like a button event, where there are two
-discrete pieces of information in the measurement.
+You can use gitbook to serve documentation. To do so, please install it using *npm* as well as *calibre* package from your package distribution manager:
+
+```bash
+sudo npm install -g gitbook-cli
+sudo apt-get install calibre
+```
+
+To generate Doxygen documentation, you'll need doxygen and graphviz:
+
+```bash
+sudo apt-get install doxygen graphviz
+```
+
+Prepare your build environment:
+
+```bash
+mkdir build && cd build
+cmake ..
+```
+
+## Generation
+
+Generate a PDF version :
+
+```bash
+gendocs.sh pdf
+```
+
+Serve an HTML version, this will run a web server that will serve you locally documentation :
+
+```bash
+gendocs.sh serve
+```
+
+Generate doxygen documentation:
+
+```bash
+gendocs.sh doxygen
+```
+or
+```bash
+cd build && make doxygen
+```
Code Review / apps / low-level-can-service.git / blobdiff