Currently, there is no way to disable the build of the umax_pp low level
sources because the tool umax_pp is *always* built. Some platforms
cannot build the umax_pp low level code so this causes problems.
The output of "net-snmp-config --cflags" can contain optimization flags.
These might not be applicable to the current compiler, causing warnings.
Use PKG_CHECK_MODULES to check for Net-SNMP and obtain the compiler and
linker flags instead, in the same way as for libcurl or poppler-glib.
On many systems now python executable it is python3.
On my system it the case and by this muild failed with:
make[2]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/backends-1.0.31/backend'
make[2]: Entering directory '/home/tkloczko/rpmbuild/BUILD/backends-1.0.31/backend'
Generating pixma/pixma_sane_options.h from pixma/pixma.c
/bin/sh: python: command not found
make[2]: *** [Makefile:7317: pixma/pixma_sane_options.h] Error 127
make[2]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/backends-1.0.31/backend'
make[2]: *** Waiting for unfinished jobs....
Using AM_PROG_PYTHON() nmacro cllows avoide tha by hecks current version of the
python and allw to use custom python executable by execute configure by:
$ PYTHON=</some/python> ./configure <params>
AM_PROG_PYTHON aclocal macro propagates to automake files $(PYTHON) variable
which could be used on geberate instaleable scripts on duting build process like
it is now in backend/Makefile.am.
Currently minum version of required vesion of the python is python >= 3.
Now that we no longer include generated files in our git repository
builds should always have maintainer mode enabled so checkouts pick
up on changes in Makefile.am, configure.ac, etc. between builds.
See #350.
CI has been using this for a long time. Now that generated files are
no longer in the repository, new clones require autotools already and
adding a git requirement doesn't seem like a big burden.
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.
baozewei