Thanks to blueagain for figuring this out.
This allows for long queries to bitcoinity to not fail
when the requested exchange/currency pair is not received
quickly enough
When you code, you should probably configure with
-Dscript_path=$HOME/your/code/dir, and doing this
now prevents the script files from being copied over
to the install dir. This is correct because in this
case source dir == dest dir.
If you want to really install the program, you
should set script_path to a relative path or a
different directory than the source. For example
-Dscript_path=duckticker/script. ninja install will
copy the script files to the install directory in
this case.
Note that the path to the script directory that
gets compiled into the binary is an absolute path
in either case. This means that "roaming app" mode
is not currently supported. The reason for this is
that I need code to detect the binary directory so
that relative script paths can work, but I don't have
that code right now.
I think I have to send 3 messages to the websocket
to initialise it. In response, it seems to send the last
ticker price reasonably quickly, compared to earlier
when it was just waiting for the next available transaction
before notifying me.
It seems to work but I think the ticker value returned
by the remote call is wrong. Maybe I'm calling the wrong
endpoint ¯\_(ツ)_/¯ I don't know trying to work it out
