-Wimplicit-function-declaration will become an error by default
in Clang 16.
Fixes errors like:
```
error: call to undeclared library function 'exit' with type 'void (int) __attribute__((noreturn))'; ISO C99 and later do not support implicit function declarations [-Werror,-Wimplicit-function-declaration]
```
Signed-off-by: Sam James <sam@gentoo.org>
Add support for Canon imageRUNNER 1018/1022/1023 models, which all share the
same USB PID. Add it as a copy of MF6500.
Tested with an iR1022A model. Flatbed and ADF both work correctly.
Signed-off-by: Michał Kopeć <michal.kopec@3mdeb.com>
minigtest.h has items that require the definitions in tests_printers.h.
Pre-GCC-12, this didn't seem to matter but GCC12 seems to have a
problem with this and requires the template definitions to have already
appeared.
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.
Tested with Avision AD345F model number DL-1802B.
Flatbed and ADF duplex scanning available.
Known limitation: ADF scanning is only capable to scan one sheet
at a time via automatic feeder. Providing 2+ sheets breaks backend
and scanner needs to be rebooted.
Signed-off-by: Nikolai Kostrigin <nickel@altlinux.org>
Tested-by: Mikhail Chernonog <snowmix@altlinux.org>
Apply formatting changes to the existing ChangeLogs for the 1.0.27 and
1.0.28 releases. (This includes re-ordering some entries so that merge
requests always appear together.) Manual formatting changes to entries
in these ChangeLogs have been preserved.
Add missing ChangeLogs for later releases.
This means that commits from the same merge request will always appear
together in the ChangeLog, instead of appearing shuffled together with
other commits that were authored around the same time.
Use 12-digit short hashes (which appear in merge commits). The number
of digits required to unambiguously identify a commit increases as the
Git repository grows. The ChangeLog for the 1.0.27 release has 7-digit
short hashes, which are no longer meaningful: 9 digits are needed now.
Forcing 12 digits to display here is the solution in the Linux kernel.
Do not "decorate" the log with branch or tag names. It is understood
that each file starts at a specific release tag (e.g. 1.0.27) and ends
at the next tag (1.0.28), or at HEAD for development snapshots. Topic
branch names, or the refs "master" and "HEAD", do not need labeling.
m. allan noah