kumquat-buildroot/package/libfastjson/libfastjson.mk

################################################################################
#
# libfastjson
#
################################################################################

LIBFASTJSON_VERSION = 0.99.8
LIBFASTJSON_SITE = $(call github,rsyslog,libfastjson,v$(LIBFASTJSON_VERSION))
LIBFASTJSON_INSTALL_STAGING = YES
LIBFASTJSON_CONF_ENV = ac_cv_prog_cc_c99='-std=gnu99'
# From git
LIBFASTJSON_AUTORECONF = YES
LIBFASTJSON_LICENSE = MIT
LIBFASTJSON_LICENSE_FILES = COPYING

$(eval $(autotools-package))
libfastjson: new package Libfastjson is a fork of json-c, and a dependency of newer versions of rsyslog. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2016-06-15 15:17:46 +02:00			`################################################################################`
			`#`
			`# libfastjson`
			`#`
			`################################################################################`

package: remove 'v' prefix from github-fetched packages On Github, a large number of projects name their tag vXYZ (i.e v3.0, v0.1, etc.). In some packages we do: <pkg>_VERSION = v0.3 <pkg>_SITE = $(call github foo,bar,$(<pkg>_VERSION)) And in some other packages we do: <pkg>_VERSION = 0.3 <pkg>_SITE = $(call github foo,bar,v$(<pkg>_VERSION)) I.e in one case we consider the version to be v0.3, in the other case we consider 0.3 to be the version. The problem with v0.3 is that when used in conjunction with release-monitoring.org, it doesn't work very well, because release-monitoring.org has the concept of "version prefix" and using that they drop the "v" prefix for the version. Therefore, a number of packages in Buildroot have a version that doesn't match with release-monitoring.org because Buildroot has 'v0.3' and release-monitoring.org has '0.3'. Since really the version number of 0.3, is makes sense to update our packages to drop this 'v'. This commit only addresses the (common) case of github packages where the prefix is simply 'v'. Other cases will be handled by separate commits. Also, there are a few cases that couldn't be handled mechanically that aren't covered by this commit. Signed-off-by: Victor Huesca <victor.huesca@bootlin.com> [Arnout: don't change flatbuffers, json-for-modern-cpp, libpagekite, python-scapy3k, softether] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> 2019-06-12 08:42:06 +02:00			`LIBFASTJSON_VERSION = 0.99.8`
			`LIBFASTJSON_SITE = $(call github,rsyslog,libfastjson,v$(LIBFASTJSON_VERSION))`
libfastjson: new package Libfastjson is a fork of json-c, and a dependency of newer versions of rsyslog. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2016-06-15 15:17:46 +02:00			`LIBFASTJSON_INSTALL_STAGING = YES`
libfastjson: indicate explicitly which gcc -std option to use This commit fixes the following build issue of libfastjson with old enough compilers (4.8) and wchar disabled: json_object.c: In function 'fjson_object_object_delete': json_object.c:385:3: error: 'for' loop initial declarations are only allowed in C99 mode for (int i = 0 ; i < FJSON_OBJECT_CHLD_PG_SIZE ; ++i) { ^ The code of libfastjson requires C99. If your compiler is recent enough (gcc 5.x), then no problem, it is C99 by default, no additional flags are needed. If your compiler is older (for example gcc 4.8), then -std=c99 or -std=gnu99 is explicitly needed to tell the compiler to accept C99 constructs. Testing the compiler for the availability of such flags is done by libfastjson configure script. However, the test program used by the configure script uses some wchar_t types, and therefore the test checking for C99 availability fails on toolchains with wchar disabled. From config.log: configure:3928: checking for /home/test/buildroot/output/host/usr/bin/i586-buildroot-linux-uclibc-gcc option to accept ISO C99 [...] configure:4077: /home/test/buildroot/output/host/usr/bin/i586-buildroot-linux-uclibc-gcc -std=gnu99 -c -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 conftest.c >&5 conftest.c:54:3: error: unknown type name 'wchar_t' const wchar_t *name; ^ So, just like we did in libv4l in commit f01396a158f14c53b781c35f7ff29da0bea8c8d6 ("libv4l: fix uclibc-ng configure/compile"), let's hint directly the configure script that it should use -std=gnu99. This fixes the build of libfastjson with old compilers and wchar disabled. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com> 2017-11-17 16:14:16 +01:00			`LIBFASTJSON_CONF_ENV = ac_cv_prog_cc_c99='-std=gnu99'`
libfastjson: new package Libfastjson is a fork of json-c, and a dependency of newer versions of rsyslog. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2016-06-15 15:17:46 +02:00			`# From git`
			`LIBFASTJSON_AUTORECONF = YES`
			`LIBFASTJSON_LICENSE = MIT`
			`LIBFASTJSON_LICENSE_FILES = COPYING`

			`$(eval $(autotools-package))`