mirror of
https://github.com/zint/zint
synced 2024-11-16 20:57:25 +13:00
7e3d0f2405
The `__has_feature` macro is a clang extension that works like a macro. If zint is being compiled using a compiler other then clang, `__has_feature` is not defined. As it is not defined, it cannot be used as a function call expression. Any environment that doesn't have `__has_feature` should prevent the preprocessor from "seeing" the invokation of the macro, as invoking undefined macros is not supported by the C language. The usual procedure to assure this would be a construction like \#if defined(__has_feature) \# if __has_feature(...) \# endif \#endif which, combined with the GCC check we have here, would result in a 3 level nesting of if and elseif expressions .. and that's without covering microsoft's compiler. For this purpose, Qt >= 5.13 has been defining the `__has_feature` macro on non-clang environments, while defining all (clang) features to not be available. This allows to write feature checks with "less" nesting, as we have here. Mimic Qt-5.13's behavior and provide the `__has_feature` macro if it's not provided otherwise (either by clang or by Qt), allowing the function-call-like expression to be parsed on those systems. |
||
---|---|---|
backend | ||
backend_qt | ||
backend_tcl | ||
cmake | ||
debian | ||
docs | ||
extras | ||
frontend | ||
frontend_qt | ||
getopt | ||
tools | ||
win32 | ||
.editorconfig | ||
.gitignore | ||
ChangeLog | ||
cmake_uninstall.cmake.in | ||
CMakeLists.txt | ||
COPYING | ||
README | ||
readme-cmake | ||
SetPaths.cmake | ||
TODO | ||
zint-qt.desktop | ||
zint-qt.png | ||
zint.nsi | ||
zint.spec |
Zint and libzint ---------------- Zint is a suite of programs to allow easy encoding of data in any of the wide range of public domain barcode standards and to allow integration of this capability into your own programs. Zint is able to encode data in the following formats: Code 11, Standard Code 2 of 5, IATA Code 2 of 5, Industrial Code 2 of 5, Interleaved Code 2 of 5, Code 2 of 5 Data Logic, ITF-14, Deutshe Post Leitcode, Deutshe Post Identcode, UPC-A, UPC-E, EAN-2, EAN-5, EAN-8, EAN-13, ISBN, UK Plessey, MSI Plessey, Telepen Alpha, Telepen Numeric, Code 39, Extended Code 39, Code 93, PZN, Code 32, LOGMARS, Codabar, Pharmacode, Code 128, GS1-128, NVE-18, Code 16k, PDF417, MicroPDF417, Two-Track Pharmacode, POSTNET, PLANET, Australia Post 4-State Symbols, RM4SCC, Dutch Post KIX, USPS Intelligent Mail, GS1 DataBar Omnidirectional, GS1 DataBar Limited, GS1 DataBar Expanded, GS1 DataBar Stacked, Composite Symbology, Data Matrix, QR Code, MaxiCode, Aztec Code, Aztec Runes, EAN-14, Micro QR, Korea Post Barcode, HIBC Code 128, HIBC Code 39, HIBC Data Matrix, HIBC PDF417, HIBC MicroPDF417, HIBC QR Code, HIBC Codablock-F, HIBC Aztec Code, Japanese Postal Code, Code 49, Channel Code, Code One, Grid Matrix, DAFT, FIM and Flattermarken, Codablock-F, DotCode, Han Xin Code, rMQR, Ultracode, UPNQR, VIN, and DPD Code. Output can be saved as BMP, EPS, GIF, PCX, TIF, EMF, PNG or SVG. PROJECT HISTORY --------------- Please see "ChangeLog" in the project root directory. CONTACT US ---------- The home of Zint is: <http://www.sourceforge.net/projects/zint> The code is now also mirrored at: <https://github.com/woo-j/zint> For feature requests or bug reports please either join the mailing list at <https://lists.sourceforge.net/lists/listinfo/zint-barcode> or add a ticket on the project's SourceForge. BEFORE POSTING TO THE LIST -------------------------- Please note the following points... * Zint is primarily developed for Linux. While we have some experience of using Zint on Windows we may be unable to resolve problems if they are specific to other operating systems. We cannot provide support for using Zint with commercial packages such as MS Office or Crystal Reports. * Always ensure you are using the latest version of Zint before posting bug reports - the bug you are reporting may have been fixed already. * Please remember to state what operating system you are using and include enough information to allow us to reproduce the error - including input data if appropriate. * Please DO NOT post messages asking for us to change the license arrangements. You will be ignored. * Please remember that Zint is developed by volunteers. While we attempt to answer all messages within a week, this is highly dependant on external circumstances.