Duane Ellis wrote:
> >> It's SIGROKDECODE_DIR actually
>
> Great, can this support >1 directory? or only 1 at a time?
Does the webpage say? Does the libsigrokdecode source say?
> BTW - This environment variable should be part of the “siggrok-cli”
> manual page
Except this environment variable
duane> Or is there a “SIGGROK_DECODERS_PATH” variable that I can use
Bert> It's SIGROKDECODE_DIR actually
Great, can this support >1 directory? or only 1 at a time?
BTW - This environment variable should be part of the “siggrok-cli” manual page
And not buried deep in some developer document.
-D
On 17/03/15 03:10, Duane Ellis wrote:
> Or is there a “SIGGROK_DECODERS_PATH” variable that I can use?
It's SIGROKDECODE_DIR actually.
This and a lot more info on writing your own protocol decoders is at:
http://sigrok.org/wiki/Protocol_decoder_HOWTO
--
Bert Vermeulen
b...@biot.com
I have SIGROK-CLI built and installed, it seems to work :-)
Now - I need to write my own decoder, and I want the decoder python source code
to be in the *current* directory, not in the installed directory.
But I do want to ‘stack’ a few existing decoders (pre-installed) with my
locally decoders
Hi,
On Fri, Mar 13, 2015 at 03:16:04PM +0100, Bartosz Golaszewski wrote:
> > This version has been reworked according to the code review by
> > Aurelien Jacobs. It now supports interleaved analog and logic packets
> > and analog frames too.
Merged, thanks!
I've given this a few quick tests with
5 matches
Mail list logo
