Older MSVC versions did not provide it.

The macOS 13.0 SDK marks `sprintf` as deprecated, causing warnings.
Follow the warnings' suggestion to switch to `snprintf`.

However, it seems that scanf does not support 8-bit sizes until MSVC 19.00.

See-also: https://web.archive.org/web/20210719202338/https://devblogs.microsoft.com/cppblog/c99-library-support-in-visual-studio-2013/

The parent project should be setting a suitable minimum version already.

Since commit fc9d607a (Use static_cast when compiling as C++,
2017-07-12) the Borland C++ 5.8 compiler is somehow confused by our
verification constructs using static_cast and fails to compile.
Fall back to C-style casts with this compiler.

Richard Jones authored 7 years ago and Brad King committed 7 years ago

The upstream RISC-V project changed some compiler symbols so `__riscv__`
must now be renamed `__riscv`.

In KWIML verification and test code we construct constant values and
cast them to specific types to see whether they are truncated or not.
Suppress MSVC diagnostic `warning C4309: 'static_cast': truncation of
constant value` since the truncation is intentional.

We did this for C-style casts in commit 5127311c (Suppress MSVC
integer cast warnings in verification and test code, 2015-12-09), but in
C++ that does not apply since commit fc9d607a (Use static_cast when
compiling as C++, 2017-07-12).

Our verification and test logic uses a few casts.  Introduce macros
to switch between C-style casts when compiling as C and static_cast
when compiling as C++.   This avoids `-Wold-style-cast` warnings.

Reported-by: Jean-Christophe Fillion-Robin <jchris.fillionr@kitware.com>

Daniel Pfeifer authored 8 years ago and Brad King committed 8 years ago

KWIML has not been updated for `include-what-you-use`.
Until this is done, block use of the tool on our own targets.
This is useful when KWIML is embedded in the source tree of
another project that may activate iwyu.

Orion Poplawski authored 8 years ago and Brad King committed 8 years ago

When compiling tests with `-Werror=format-security` we get

    error: -Wformat-security ignored without -Wformat

Therefore we should disable both `format` and `format-security` together.

Richard Jones authored 8 years ago and Brad King committed 8 years ago

Signed-off-by: Richard W.M. Jones <rjones@redhat.com>

When referencing `int#_t` and `uint#_t` types in `KWIML_INT_*_t` macros,
use an explicit `::` in C++ to reference the global namespace.  This
allows the macros to be used inside other namespaces even if they have
typedefs for the types too.

Use a long conflict marker size to avoid confusion with section header
underlines.

In KWIML verification and test code we construct constant values and
cast them to specific types to see whether they are truncated or not.
Suppress MSVC diagnostic `warning C4310: cast truncates constant value`
since the truncation is intentional.

Marek Vasut authored 9 years ago and Brad King committed 9 years ago

Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Ley Foon Tan <lftan@altera.com>
Cc: Thomas Chou <thomas@wytron.com.tw>
Cc: Walter Goossens <waltergoossens@home.nl>

Files distributed only with our source tree reference Copyright.txt
for details.  Simplify the blocks making this reference since they
will never be distributed as part of an installation.

In this mode do not provide the CMake package files or `version.h`
header.  Instead KWIML will be distributed with and versioned with the
host project.

Provide the KWIML version number and the availability of each other
header with this version.

Enable `find_package(kwiml 1.0)` to find KWIML by providing CMake
package configuration and version files from the build and install
trees.  Within the package provide a `kwiml::kwiml` INTERFACE library
encoding the include directories as a usage requirement.

Provide KWIML_ABI_VERSION and KWIML_INT_VERSION interface version macros
as the latest version among those included so far.  Guard against
definition of an interface version that has already been defined.  This
way we can provide the current version's interface even if an older or
newer version has been included earlier in the translation unit.  The
result will be a union of all interfaces provided by all versions
included.

Add the interface version numbers to the verification "extern" symbols
so that each version can verify that it provides what is expected even
if it inherited an existing value from another version included earlier.
Guard against multiple verification of the same version.

Avoid using the reserved `__` in symbol names (except for macros related
to `__int64`).  Instead use `_private_` for private implementation
details that should not be exposed to includers.  Use `_detail`_ for
implementation details that we must expose to includers but that they
should not use.

We use the common convention for boolean macros to leave them undefined
for false and defining them to 1 for true.  Fix some cases where we
define a boolean macro for true but did not set it to 1.

Guard definition of every public macro with a condition that it is not
already defined in the translation unit.  This will allow project code
or command-line definitions to override any value we select.  It will
also provide granular guards against repeat inclusion of this header if
we were to remove the top-level include guard.

Avoid leaking them to includers.

Guard inclusion of stdint.h and inttypes.h with a dedicated preprocessor
macro.  This avoids asking the preprocessor to read the files again just
to hit their include guards.

Improve the names of the macros implementing verification steps.

Drop use of configured header files and simply hard code the name
"kwiml".  This will allow distribution as a separate project that can be
installed on a system and included as a dependency by clients.

While at it, rename "ABI" to "abi" and "INT" to "int" in file names and
test function names.  We will use upper-case names only for macro names.

Max Filippov authored 10 years ago and Brad King committed 10 years ago

Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>

Ben Boeckel authored 10 years ago and Brad King committed 10 years ago

When testing CMAKE_<LANG>_COMPILER_ID values with if(STREQUAL), do not
explicitly dereference or quote the variable.  We want if() to
auto-dereference the variable and not its value.

Christian Svensson authored 10 years ago and Brad King committed 10 years ago

It defines __or1k__ and is big endian.

Old GNU compilers do not define __SIZEOF_LONG_LONG__ or
__LONG_LONG_MAX__ but do provide a 64-bit 'long long' type.

Suggested-by: Rolf Eike Beer <eike@sf-mail.de>

Riku Voipio authored 12 years ago and Brad King committed 12 years ago

The __aarch64__ defines Aarch64, while __AARCH64EB__ defines bigendian
and __AARCH64EL__ little endian.  Only little endian tested, no big
endian toolchain exists yet.

Signed-off-by: Riku Voipio <riku.voipio@linaro.org>