The substitute completely ignores the fdtype argument and only works
correctly for S_IFSOCK values. This happened to be the only way the
function was invoked but for safety's sake this has been replaced by
a local implementation that does pretty much the same thing, without
the misleading bit.
Found courtesy of a [-Wunused-parameter] compiler warning on Alpine.
This:
- modifies `configure.ac` to get a version number courtesy of `git`
when `autoconf` is run
- runs a `make dist` when all compilation targets succeed
- makes the resulting tarball available as a build artifact
- renames the various pipeline stages
There is no need to depend on and link in all the various dependencies
for whatever backends *might* be preloaded if none are. Distributions
habitually rip these out, rightfully so, to reduce the list of package
dependencies. This will achieve the same while still doing the "right
thing" for builds that do preload one or more backens.
Moved old changelogs to new directory, and excluded them from
release tarball.
Improved release docs.
Updated config.* files
Bumped version numbers.
Wrote release notes.
If none of the formats can be generated but API specs are requested,
bomb. The original test aimed to do so but was testing against "no",
a value that was never assigned.
This fixes a [-Wpedantic] compiler warning about ISO C forbidding empty
translation units. The check-usb-chip.c file reduces to such a file in
the case USB support was explicitly disabled or no usable library found.
This utility has less dependencies and supports conversion to a pile of
other formats that may come in handy as well.
Clean up of generated PDF figures has been moved to the clean target as
well.
Unless explicitly asked to do without, all formats for which required
tools are found will be built. Checks cover PostScript, PDF and HTML.
All logic and files involved are now collected in a single "section"
and grouped in such a way that their function should be clearer.
fixup! Refactor API spec conversion support
When libusb-1.0 is not found, libusb-0.1 will be tried. On BeOS and
OS2, nothing should have changed in terms of detection of USB support.
On all systems the --enable-libusb* flags are now ignored. Instead, the
--with-usb and --without-usb flags now control support. When neither is
given USB support will be enable if possible and disabled otherwise. If
--with-usb is requested but not possible, ./configure will fail. There
is no support to prefer libusb-0.1 over libusb-1.0.
This ought to get rid of the last empty compilation unit warnings. This
merges libfelib.la with liblib.la. The former was always used together
with the latter. The latter was only ever used without the former when
linking backends and tools.
Tools might want to use the getopt functions, backends might just want
to use MD5.
The references in in-file changelogs and the ChangeLog files have not
been modified. Only those references that refer to current practices
or locations.
The distclean target should only remove files that make creates. If
there are any that need taking care of, they should be added in on a
per file basis in the Makefile.am that creates it.
Upon re-reading the autoconf documentation, this seemed the right thing
to do. The AC_LANG_PROGRAM macro does not quote its arguments so any
occurence of [ and ] will get stripped out if not double quoted.
Current code snippets passed do not use them but it is better to use a
consistent quoting approach for such snippets. In other places in the
configure.ac file double quoting is used already.
This gets rid of a number of obsoleted macros and replaces RETSIGTYPE
with a void literal which can be assumed for C89 and later.
This changeset was prepared using autoupdate and modified to get rid of
whitespace and doubled [] changes. Changes to acinclude.m4 were added
by hand.
Several variables are considered "user variables" by the GNU Standards.
This means that the user can pass these to their ./configure and make
invocations as they see fit. These variables include CPPFLAGS, CFLAGS
and LDFLAGS.
This changeset pushes our use of these variables to the automake shadow
variables, AM_CPPFLAGS, AM_CFLAGS and AM_LDFLAGS, so that user variables
will no longer clobber flags required in order to build.
This addresses autoreconf output such as:
tools/Makefile.am:37: warning: source file '../backend/sane_strstatus.c' is in a subdirectory,
tools/Makefile.am:37: but option 'subdir-objects' is disabled
The option was introduced in automake version 1.9 and is slated for
unconditional activation with automake-2.0.
Olaf Meeuwissen