Throw clang into the matrix, so we get a bit of extra coverage. As
evidenced by the disabled warning - it does catch extra issues.
Currently enabled only for 64bit builds, since fiddling with environment
variables and cross-files is more tricky than I can be asked atm x-D
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
The list.h code is REALLY old, from a very old kernel version. Import
the CCAN version instead, and move the code to use it. This is in
anticipation of fixing up the memory leaks in this area.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
The former is clang-only, which has been clean for a while. While the
latter is gone with the hash tables removal as of earlier commits.
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
Move the files into designated place, so they're easier to find and
reason with.
While in here, simplify the install_man() call to only include the
strings. Meson will convert them to files() and deduce the correct path
based on the file extension.
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
The usbhid-dump project effectively lives in this repo (it was a git
module ages ago), so there's little point in the separate build file(s).
People can still build usbhid-dump alone, as below:
ninja -C builddir/ usbhid-dump
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
With the API fixed and most data annotated as read-only, we can flip the
warning back on.
In theory all the arrays in usb-spec.h can be make constant, although
atm the entries have link to other (hashed) entries and is populated at
program startup.
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
Random collection of bits from other projects that I hack on. The
suggestions are currently disabled until resolved.
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
The code is warning free, so flip those on. Flip the Wformat=2 and
Wformat order, since the latter is =1 and overrides the former.
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
The latter warns on missing cases in the switch. The former also warns
even if there is a default statement. We extensively use defaults so,
opt for the saner warning.
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
With the earlier commits we've removed any processing done on these
in(put) files. Just rename them to their final form.
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
Provides false-warnings, we are handling "unknown" enums with a
"default:" line in the switch statement in lsusb.c, yet gcc still
complains about it for some reason. So disable the compiler warning
until the compilers are fixed.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Add all the flags, apart from -Werror and -fdiagnostics-color=auto.
We don't want for the former in the default build, but for developer,
maintainer and/or CI builds ... Some patches adding CI, fixing the
warnings, etc will be coming later on.
The latter overrides the default color handling, so we cannot see them
pretty colo(u)rs ;-P
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
Make the inline comment a reality ;-) Apart from -g -Wall that is...
The latter is already set by default with warning_level=1 (we use 2) and
the former belongs in a developer file, coming with a later series.
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
Seems like we've (tried) to fix this in the past, although it crept in
again. Just use a compiler directive and drop the error prone individual
includes.
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
List the licenses, add minimum meson version, C standard, warning level
and default prefix.
- licenses - non-authoritative, a decent indication
- meson 0.60 - like mesa, systemd, kmod, available in Debian old-stable
- gnu99 - bit of a guess work, c99 definitely chokes
- warning_level=2 - equivalent to -Wall -Wextra
- prefix /usr like the autotools build
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
Bump the required version to 1.0.22, as available in Debian 10
(old-old-stable), released ~6 years ago.
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
Autotools is great for what it is designed for, but that epoch is long
ago, and shipping random files/scripts that are not actually checked
into the build system is ripe for problems.
Convert the build over to use meson instead. Bonus is that the build
logic is simpler (if not still messy in places), and that the build
itself is way faster.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
