| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
0.5.0 will be the next major, API-changing release. Bump now, so that
there is no confusion of tarball 0.4.0 and 0.5.0-git snapshots.
|
|
The last release (0.3.0) had the libtool version (current:revision:age)
set to 2:0:0. Since this release removes and changes interfaces, the new
version is 3:0:0.
http://www.gnu.org/software/libtool/manual/libtool.html#Updating-version-info
This changes the library filename (e.g. on Linux) from
libsigrokdecode.so.2.0.0 to libsigrokdecode.so.3.0.0, the SONAME
(+symlink) becomes libsigrokdecode.so.3.
|
|
This fixes bug #739.
|
|
This is needed for e.g. g_slist_free_full(), which incidentally
has been in use for a while already.
|
|
|
|
Do not redefine it though when already set, so that it can be
overridden by the user, or indirectly by the compiler settings.
|
|
Also output the compiler version in the configuration summary.
|
|
|
|
|
|
In order to avoid confusion of the flags-gathering pkg-config
result with the actual test for the availability of "check",
change the pkg-config output variable prefix from CHECK to TESTS.
|
|
|
|
|
|
This avoids confusion with the released tarballs.
|
|
Drop them from the libsigrokdecode repository.
|
|
CFLAGS, CPPFLAGS, LDFLAGS and so on are so-called "user variables" and
are meant for users of the package to use/override. The package itself
should not set or modify them in any way. Instead, the "shadow variables"
such as AM_CFLAGS, AM_CPPFLAGS, AM_LDFLAGS and so on, can be modified by
the package.
|
|
Only the unittests use these flags, so don't go linking them in for
the main library too.
|
|
The == operator is not in POSIX.
|
|
The current libsigrokdecode build passes the python
CPPFLAGS and LDFLAGS directly into libsigrokdecode.pc.in.
This leads to issues while cross-compiling as while using
PKG_CONFIG_SYSROOT_DIR, there is a chance of the prefix
being duplicated. We now, while detecting the installation
of python (cross or normal), add a dependency for the
module name in the pkgconfig file (from configure.ac).
|
|
|
|
The libtool current:revision:age numbers change from 1:0:0 to 2:0:0.
Details:
http://www.gnu.org/software/libtool/manual/libtool.html#Updating-version-info
This changes the library filename (e.g. on Linux) from
libsigrokdecode.so.1.0.0 to libsigrokdecode.so.2.0.0, the SONAME (+symlink)
becomes libsigrokdecode.so.2.
|
|
|
|
Sometimes the Python 3 executable is called just 'python3', sometimes
it is called 'python3.4' and so on. Handle all cases transparently for
the user.
Before:
$ make install
/usr/bin/env: python3: No such file or directory
After:
$ make install
python3.4 ./tools/install-decoders -i ./decoders -o [...]
Installing 36 protocol decoders:
[...]
|
|
|
|
(fewer files, less clutter)
|
|
Also, drop printing of the detected Python CPPFLAGS/LDFLAGS, not really
needed since it's available in 'make V=1' output as well (and we don't print
it for other libs either).
|
|
We use some functions specific to 3.1, but every distribution appears
to be at 3.2.x already anyway.
|
|
|
|
Drop checks where we don't use the result (yet). We might bring back
some of those once we start actually using the result in the code.
|
|
We just use dummy/fake python3.pc files on Windows so that the usual
pkg-config mechanism works there as well.
|
|
Even when using pkg-config not all distro/platform specific issues are
transparent, unfortunately. On some systems the pkg-config file is
named "python3.pc" on others it's versioned, e.g. "python-3.2.pc".
See also: http://sigrok.org/wiki/Libsigrokdecode/Python
This should fix the build on e.g. FreeBSD, NetBSD, Mac OS X (some
versions), and possibly various Linux distros, e.g. Gentoo.
Also, drop manual AC_MSG_ERROR() and let PKG_CHECK_MODULES() output a
more verbose and standardized error message if Python 3 is not found.
|
|
The python3-config script reported "-lm" as linker option previously,
but we switched to using pkg-config (among other things for
cross-compile support) which doesn't report "-lm" though (this is a
common behaviour across multiple distros and OSes).
|
|
Using python-config does not work when cross-compiling, since it
can only be run on the host system.
|
|
|
|
This only compiles libsigrok into the one target that needs it, instead
of slopping it all over the place.
|
|
This adds a tool in the tests directory, called pdtest. It uses the
"test/" directory in every PD directory, if present, to run the
PD against dumps found in the sigrok-dumps repository, and compares
the output against ".output" files in the "test/" directory. The file
"test/test.conf" is used to configure which tests to run.
A separate tool (tests/runtc.c) is used to run the actual decoding and
report output.
To get an overview of the options, run tests/pdtest without any options.
|
|
|
|
|
|
This PD tries to guess / detect / estimate a bitrate of e.g. some
UART communication snippet or other protocols.
|
|
|
|
This uses the Check unit testing framework, just like libsigrok.
For now, only a few very basic unit tests are included.
Invocation:
make check
|
|
This stacks of top of the 'i2s' decoder and outputs the audio data to
file (or stdout) in various formats. Currently only WAV is supported.
This is work in progress, it has various hard-coded assumptions.
|
|
There will be further PDs that are stacked on top of usb_packet.
|
|
This supports a certain number of MIDI messages already, but not yet all
of them. More will be added later.
|
|
|
|
This matches the convention used in libsigrok. Potential other headers
might end up in libsigrokdecode/, but only libsigrokdecode.h is meant
to be #included by frontends directly.
|
|
|
|
|
