mirror of
https://git.code.sf.net/p/zint/code
synced 2025-12-17 09:57:02 +00:00
[f3a982c1dd])
AZTEC/CODE16K/CODEONE/DATAMATRIX/DBAR_EXP/GRIDMATRIX/HANXIN
/MAILMARK_4S/PDF417/MSI_PLESSEY/QRCODE/RMQR/TIF/ULTRA/USPS_IMAIL:
lessen storage of some tables by using least integral size
required (saves ~3K); reformat some tables, comments
AUSPOST/AZTEC: remove unnecessary int casts on array indexing
CODE11/CODE39: move start/stop chars into one entry in tables to
save a few bytes; some reformatting, comments
CODEONE: add `c1_` prefixes
common: more precise compiler/version checks
composite: add `cc_` prefixes; UINT -> unsigned short; use
`sizeof()` instead of `strlen()` for `in_linear_comp` static;
some reformatting, comments
EMF: use table instead of string for `ultra_chars[]`
GIF: remove unnecessary cast
library: use `sizeof()` instead of `strlen()` for static;
add `consts` to `escape_char_process()` & use unsigned for `ch`
DBAR: use `dbar_`, `dbar_ltd_`, `dbar_exp_` prefixes
docs: update pandoc version
% frontend/tests/README 2024-01-12
Zint frontend test suite
------------------------
See <project-dir>/backend/tests/README to see how to build the test suite.
In addition to the setup for the backend tests, the environment needs to be
able to find the `zint` application using that name. In UNIX-like systems
this can be configured by prepending the PATH variable with the frontend's
directory inside the build directory:
cd <build-dir>
export PATH=$(pwd)/frontend:${PATH}
------------------------------------------------------------------------------
the frontend test will be automatically run by cmake's ctest, however manual
invocation is also possible:
cd <build-dir>/frontend/test
./test_args
As with the backend tests, individual test functions and single dataset items
can be run using '-f <func-name>' and '-i <index>' etc.