Max external objects for interacting with chainAPI (formerly called MAXChain).
brew install cmake
git clone email@example.com:eflynch/chainflow cd chainflow git submodule init git submodule update
To do a universal build of jansson which is a library for JSON in C
cd jansson mkdir build cd build cmake .. "-DCMAKE_OSX_ARCHITECTURES:=x86_64;i386" make cd ../..
To do a universal build of libwebsockets do the following. I don't really understand why this sequence of operations works. If you try to do the second cmake command without having first done the first you will encounter compiler errors when you run make.
cd libwebsockets mkdir build cd build cmake .. -DCMAKE_C_FLAGS='-arch i386' make cmake .. -DCMAKE_C_FLAGS='-arch i386 -arch x86_64' make cd ../..
This sequence has been provided as a shell script in
Each external can be built with it's own XCode project or you can use the convenience Makefile to build them all at once.
ChainFlow consists of a set of Max external objects that interact with eachother and collectively provide an interface for accessing spatially distributed time-series data hosted by chainAPI server. See Help files for documentation on specific objects.
- "site" - a collection of devices, sensors, and their data
- "device" - a location in space associated with one or more streams of time-series data usually corresponding to a real-world physical device carrying sensors
- "metric" - a type of time-series data (e.g. "humidity", "temperature")
[chain.site] object manages a connection to a chainAPI server. The other
[chain.*] objects need to be attached to an instance of
[chain.site] which manages them. The first and only argument to all
[chain.*] objects is an identifier to associate workers with a site. This defaults to a genric identifier "defaul_site." Each instance of
[chain.site] should be given a unique identifier.