Skip to contentSkip to conversation

kyua: new package and dependencies

PATCH Superseded Sebastien Bourdelin 3 participants 11 messages Jun 7, 2015 – Jun 11, 2015

v3 of 5 Superseded Latest is v5 →

lore
Share & tools
lore
#0 lore raw

v3 cover kyua: new package and dependencies

This patchset introduces the Kyua testing framework with its dependencies.

https://github.com/jmmv/kyua

Sebastien Bourdelin (3):
atf: new package
lutok: new package
kyua: new package

 package/Config.in       |  3 +++
 package/atf/Config.in   | 11 +++++++++++
 package/atf/atf.hash    |  2 ++
 package/atf/atf.mk      | 21 +++++++++++++++++++++
 package/kyua/Config.in  | 18 ++++++++++++++++++
 package/kyua/kyua.hash  |  2 ++
 package/kyua/kyua.mk    | 26 ++++++++++++++++++++++++++
 package/lutok/Config.in | 11 +++++++++++
 package/lutok/lutok.mk  | 19 +++++++++++++++++++
 9 files changed, 113 insertions(+)
 create mode 100644 package/atf/Config.in
 create mode 100644 package/atf/atf.hash
 create mode 100644 package/atf/atf.mk
 create mode 100644 package/kyua/Config.in
 create mode 100644 package/kyua/kyua.hash
 create mode 100644 package/kyua/kyua.mk
 create mode 100644 package/lutok/Config.in
 create mode 100644 package/lutok/lutok.mk
Signature · 1 line
2.4.0
#1 lore raw

PATCH v3 1/3 atf: new package

ATF, or Automated Testing Framework, is a collection of libraries to write test programs in C, C++ and POSIX shell.

https://github.com/jmmv/atf

---
Changes v2 -> v3:
- rebase

suggested by Arnout Vandecapelle <[email protected]>:
- adds comment to explain the need to use AUTORECONF

Changes v1 -> v2:
suggested by Arnout Vandecapelle <[email protected]>:
- bump the version
- uses the release archive instead of the github automatic one
- updates the hash
- removes host-pkgconf from dependencies
- changes the license
- reworks the comment around CONF_ENV to avoid error

---
 package/Config.in     |  1 +
 package/atf/Config.in | 11 +++++++++++
 package/atf/atf.hash  |  2 ++
 package/atf/atf.mk    | 23 +++++++++++++++++++++++
 4 files changed, 37 insertions(+)
 create mode 100644 package/atf/Config.in
 create mode 100644 package/atf/atf.hash
 create mode 100644 package/atf/atf.mk
package/Config.in +1 -0
index e0c2e2a..78ed223 100644
@@ -57,6 +57,7 @@ endif
 endmenu
 
 menu "Debugging, profiling and benchmark"
+	source "package/atf/Config.in"
 	source "package/blktrace/Config.in"
 	source "package/bonnie/Config.in"
 	source "package/cache-calibrator/Config.in"
package/atf/Config.in new file +11 -0
new file mode 100644
index 0000000..59712ab
@@ -0,0 +1,11 @@
+config BR2_PACKAGE_ATF
+	bool "atf"
+	depends on BR2_INSTALL_LIBSTDCPP
+	help
+	  ATF, or Automated Testing Framework, is a collection of
+	  libraries to write test programs in C, C++ and POSIX shell.
+
+	  https://github.com/jmmv/atf
+
+comment "atf needs a toolchain w/ C++"
+	depends on !BR2_INSTALL_LIBSTDCPP
package/atf/atf.hash new file +2 -0
new file mode 100644
index 0000000..78cd3c6
@@ -0,0 +1,2 @@
+# Locally computed
+sha256 92bc64180135eea8fe84c91c9f894e678767764f6dbc8482021d4dde09857505 atf-0.21.tar.gz
package/atf/atf.mk new file +23 -0
new file mode 100644
index 0000000..bf6f156
@@ -0,0 +1,23 @@
+################################################################################
+#
+# atf
+#
+################################################################################
+
+ATF_VERSION = 0.21
+ATF_SITE = https://github.com/jmmv/atf/releases/download/atf-$(ATF_VERSION)
+ATF_INSTALL_STAGING = YES
+ATF_LICENSE = BSD-3c
+ATF_LICENSE_FILES = COPYING
+# Ships a beta libtool version hence our patch doesn't apply.
+ATF_AUTORECONF = YES
+
+
+# ATF_SHELL defaults to the host's bash
+ATF_CONF_ENV = \
+	kyua_cv_getopt_plus=yes \
+	kyua_cv_attribute_noreturn=yes \
+	kyua_cv_getcwd_works=yes \
+	ATF_SHELL=/bin/sh
+
+$(eval $(autotools-package))
Signature · 1 line
2.4.0
#2 lore raw

PATCH v3 1/3 atf: new package

Dear Sebastien Bourdelin,

package/Config.in endif · line 60

Quoted 2 lines · Sebastien Bourdelin

menu "Debugging, profiling and benchmark"

package/Config.in +1 -0
+	source "package/atf/Config.in"

Is "Debugging, profiling and benchmark" the right place? It seems to be more like the gtest package, which is in Libraries -> Other.

But agreed, we don't really have a good place for test related libraries/frameworks. Maybe we should create one?

Quoted 18 lines

new file mode 100644
index 0000000..bf6f156

package/atf/atf.mk new file +13 -0
@@ -0,0 +1,23 @@
+################################################################################
+#
+# atf
+#
+################################################################################
+
+ATF_VERSION = 0.21
+ATF_SITE = https://github.com/jmmv/atf/releases/download/atf-$(ATF_VERSION)
+ATF_INSTALL_STAGING = YES
+ATF_LICENSE = BSD-3c
+ATF_LICENSE_FILES = COPYING
+# Ships a beta libtool version hence our patch doesn't apply.
+ATF_AUTORECONF = YES

package/atf/atf.mk line 23

Quoted 10 lines
package/atf/atf.mk new file +10 -0
+
+
+# ATF_SHELL defaults to the host's bash
+ATF_CONF_ENV = \
+	kyua_cv_getopt_plus=yes \
+	kyua_cv_attribute_noreturn=yes \
+	kyua_cv_getcwd_works=yes \
+	ATF_SHELL=/bin/sh
+
+$(eval $(autotools-package))

It installs quite a bunch of things to the target filesystem, including C and C++ source code, which seems a bit useless since we don't support building/installing a compiler for the target:

./usr/tests/atf
./usr/tests/atf/Kyuafile
./usr/tests/atf/atf-sh
./usr/tests/atf/atf-sh/tc_test
./usr/tests/atf/atf-sh/Kyuafile
./usr/tests/atf/atf-sh/atf-check_test
./usr/tests/atf/atf-sh/tp_test
./usr/tests/atf/atf-sh/integration_test
./usr/tests/atf/atf-sh/misc_helpers
./usr/tests/atf/atf-sh/normalize_test
./usr/tests/atf/atf-sh/config_test
./usr/tests/atf/atf-sh/atf_check_test
./usr/tests/atf/atf-c
./usr/tests/atf/atf-c/tc_test
./usr/tests/atf/atf-c/Kyuafile
./usr/tests/atf/atf-c/atf_c_test
./usr/tests/atf/atf-c/macros_test
./usr/tests/atf/atf-c/tp_test
./usr/tests/atf/atf-c/build_test
./usr/tests/atf/atf-c/error_test
./usr/tests/atf/atf-c/check_test
./usr/tests/atf/atf-c/utils_test
./usr/tests/atf/atf-c/pkg_config_test
./usr/tests/atf/atf-c/macros_h_test.c
./usr/tests/atf/atf-c/unused_test.c
./usr/tests/atf/atf-c/detail
./usr/tests/atf/atf-c/detail/version_helper
./usr/tests/atf/atf-c/detail/env_test
./usr/tests/atf/atf-c/detail/Kyuafile
./usr/tests/atf/atf-c/detail/process_test
./usr/tests/atf/atf-c/detail/fs_test
./usr/tests/atf/atf-c/detail/text_test
./usr/tests/atf/atf-c/detail/dynstr_test
./usr/tests/atf/atf-c/detail/sanity_test
./usr/tests/atf/atf-c/detail/list_test
./usr/tests/atf/atf-c/detail/user_test
./usr/tests/atf/atf-c/detail/process_helpers
./usr/tests/atf/atf-c/detail/map_test
./usr/tests/atf/atf-c++
./usr/tests/atf/atf-c++/atf_c++_test
./usr/tests/atf/atf-c++/macros_hpp_test.cpp
./usr/tests/atf/atf-c++/Kyuafile
./usr/tests/atf/atf-c++/tests_test
./usr/tests/atf/atf-c++/macros_test
./usr/tests/atf/atf-c++/build_test
./usr/tests/atf/atf-c++/check_test
./usr/tests/atf/atf-c++/utils_test
./usr/tests/atf/atf-c++/pkg_config_test
./usr/tests/atf/atf-c++/unused_test.cpp
./usr/tests/atf/atf-c++/detail
./usr/tests/atf/atf-c++/detail/version_helper
./usr/tests/atf/atf-c++/detail/env_test
./usr/tests/atf/atf-c++/detail/Kyuafile
./usr/tests/atf/atf-c++/detail/process_test
./usr/tests/atf/atf-c++/detail/exceptions_test
./usr/tests/atf/atf-c++/detail/fs_test
./usr/tests/atf/atf-c++/detail/application_test
./usr/tests/atf/atf-c++/detail/text_test
./usr/tests/atf/atf-c++/detail/auto_array_test
./usr/tests/atf/test-programs
./usr/tests/atf/test-programs/srcdir_test
./usr/tests/atf/test-programs/Kyuafile
./usr/tests/atf/test-programs/c_helpers
./usr/tests/atf/test-programs/sh_helpers
./usr/tests/atf/test-programs/expect_test
./usr/tests/atf/test-programs/config_test
./usr/tests/atf/test-programs/meta_data_test
./usr/tests/atf/test-programs/cpp_helpers
./usr/tests/atf/test-programs/result_test

Are all of these files needed on the target?

Thanks,

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
#3 lore raw

PATCH v3 1/3 atf: new package

Hi Thomas.

I will leave you that choice :)

Thanks.

Quoted 119 lines · Thomas Petazzoni

Dear Sebastien Bourdelin,

package/Config.in endif · line 60

Quoted 2 lines · Sebastien Bourdelin

menu "Debugging, profiling and benchmark"

package/Config.in +1 -0
+	source "package/atf/Config.in"

Is "Debugging, profiling and benchmark" the right place? It seems to be more like the gtest package, which is in Libraries -> Other.

But agreed, we don't really have a good place for test related libraries/frameworks. Maybe we should create one?

Quoted 18 lines

new file mode 100644
index 0000000..bf6f156

package/atf/atf.mk new file +13 -0
@@ -0,0 +1,23 @@
+################################################################################
+#
+# atf
+#
+################################################################################
+
+ATF_VERSION = 0.21
+ATF_SITE = https://github.com/jmmv/atf/releases/download/atf-$(ATF_VERSION)
+ATF_INSTALL_STAGING = YES
+ATF_LICENSE = BSD-3c
+ATF_LICENSE_FILES = COPYING
+# Ships a beta libtool version hence our patch doesn't apply.
+ATF_AUTORECONF = YES

package/atf/atf.mk line 23

Quoted 10 lines
package/atf/atf.mk new file +10 -0
+
+
+# ATF_SHELL defaults to the host's bash
+ATF_CONF_ENV = \
+	kyua_cv_getopt_plus=yes \
+	kyua_cv_attribute_noreturn=yes \
+	kyua_cv_getcwd_works=yes \
+	ATF_SHELL=/bin/sh
+
+$(eval $(autotools-package))

It installs quite a bunch of things to the target filesystem, including C and C++ source code, which seems a bit useless since we don't support building/installing a compiler for the target:

./usr/tests/atf
./usr/tests/atf/Kyuafile
./usr/tests/atf/atf-sh
./usr/tests/atf/atf-sh/tc_test
./usr/tests/atf/atf-sh/Kyuafile
./usr/tests/atf/atf-sh/atf-check_test
./usr/tests/atf/atf-sh/tp_test
./usr/tests/atf/atf-sh/integration_test
./usr/tests/atf/atf-sh/misc_helpers
./usr/tests/atf/atf-sh/normalize_test
./usr/tests/atf/atf-sh/config_test
./usr/tests/atf/atf-sh/atf_check_test
./usr/tests/atf/atf-c
./usr/tests/atf/atf-c/tc_test
./usr/tests/atf/atf-c/Kyuafile
./usr/tests/atf/atf-c/atf_c_test
./usr/tests/atf/atf-c/macros_test
./usr/tests/atf/atf-c/tp_test
./usr/tests/atf/atf-c/build_test
./usr/tests/atf/atf-c/error_test
./usr/tests/atf/atf-c/check_test
./usr/tests/atf/atf-c/utils_test
./usr/tests/atf/atf-c/pkg_config_test
./usr/tests/atf/atf-c/macros_h_test.c
./usr/tests/atf/atf-c/unused_test.c
./usr/tests/atf/atf-c/detail
./usr/tests/atf/atf-c/detail/version_helper
./usr/tests/atf/atf-c/detail/env_test
./usr/tests/atf/atf-c/detail/Kyuafile
./usr/tests/atf/atf-c/detail/process_test
./usr/tests/atf/atf-c/detail/fs_test
./usr/tests/atf/atf-c/detail/text_test
./usr/tests/atf/atf-c/detail/dynstr_test
./usr/tests/atf/atf-c/detail/sanity_test
./usr/tests/atf/atf-c/detail/list_test
./usr/tests/atf/atf-c/detail/user_test
./usr/tests/atf/atf-c/detail/process_helpers
./usr/tests/atf/atf-c/detail/map_test
./usr/tests/atf/atf-c++
./usr/tests/atf/atf-c++/atf_c++_test
./usr/tests/atf/atf-c++/macros_hpp_test.cpp
./usr/tests/atf/atf-c++/Kyuafile
./usr/tests/atf/atf-c++/tests_test
./usr/tests/atf/atf-c++/macros_test
./usr/tests/atf/atf-c++/build_test
./usr/tests/atf/atf-c++/check_test
./usr/tests/atf/atf-c++/utils_test
./usr/tests/atf/atf-c++/pkg_config_test
./usr/tests/atf/atf-c++/unused_test.cpp
./usr/tests/atf/atf-c++/detail
./usr/tests/atf/atf-c++/detail/version_helper
./usr/tests/atf/atf-c++/detail/env_test
./usr/tests/atf/atf-c++/detail/Kyuafile
./usr/tests/atf/atf-c++/detail/process_test
./usr/tests/atf/atf-c++/detail/exceptions_test
./usr/tests/atf/atf-c++/detail/fs_test
./usr/tests/atf/atf-c++/detail/application_test
./usr/tests/atf/atf-c++/detail/text_test
./usr/tests/atf/atf-c++/detail/auto_array_test
./usr/tests/atf/test-programs
./usr/tests/atf/test-programs/srcdir_test
./usr/tests/atf/test-programs/Kyuafile
./usr/tests/atf/test-programs/c_helpers
./usr/tests/atf/test-programs/sh_helpers
./usr/tests/atf/test-programs/expect_test
./usr/tests/atf/test-programs/config_test
./usr/tests/atf/test-programs/meta_data_test
./usr/tests/atf/test-programs/cpp_helpers
./usr/tests/atf/test-programs/result_test

Are all of these files needed on the target?

Thanks,

Thomas

#4 lore raw

PATCH v3 1/3 atf: new package

Quoted 7 lines · Sebastien Bourdelin

Hi Thomas.

I will leave you that choice :)

Thanks.

On 06/11/2015 04:33 PM, Thomas Petazzoni wrote:

[snip]

Quoted 3 lines
Quoted 3 lines

It installs quite a bunch of things to the target filesystem, including C and C++ source code, which seems a bit useless since we don't support building/installing a compiler for the target:

Sebastien, could you still respond to this question? AFAICS, Thomas is right,
these tests actually test atf itself so they shouldn't be installed, or they should be cleaned up in a POST_TARGET_INSTALL_HOOK. I think the easiest is not to install them, by setting

ATF_INSTALL_TARGET_OPTS = DESTDIR=$(TARGET_DIR) install-exec

This installs only the libraries and the atf-sh program, which I think is all
that is needed.

Regards,
Arnout

Quoted 88 lines
Quoted 71 lines

./usr/tests/atf
./usr/tests/atf/Kyuafile
./usr/tests/atf/atf-sh
./usr/tests/atf/atf-sh/tc_test
./usr/tests/atf/atf-sh/Kyuafile
./usr/tests/atf/atf-sh/atf-check_test
./usr/tests/atf/atf-sh/tp_test
./usr/tests/atf/atf-sh/integration_test
./usr/tests/atf/atf-sh/misc_helpers
./usr/tests/atf/atf-sh/normalize_test
./usr/tests/atf/atf-sh/config_test
./usr/tests/atf/atf-sh/atf_check_test
./usr/tests/atf/atf-c
./usr/tests/atf/atf-c/tc_test
./usr/tests/atf/atf-c/Kyuafile
./usr/tests/atf/atf-c/atf_c_test
./usr/tests/atf/atf-c/macros_test
./usr/tests/atf/atf-c/tp_test
./usr/tests/atf/atf-c/build_test
./usr/tests/atf/atf-c/error_test
./usr/tests/atf/atf-c/check_test
./usr/tests/atf/atf-c/utils_test
./usr/tests/atf/atf-c/pkg_config_test
./usr/tests/atf/atf-c/macros_h_test.c
./usr/tests/atf/atf-c/unused_test.c
./usr/tests/atf/atf-c/detail
./usr/tests/atf/atf-c/detail/version_helper
./usr/tests/atf/atf-c/detail/env_test
./usr/tests/atf/atf-c/detail/Kyuafile
./usr/tests/atf/atf-c/detail/process_test
./usr/tests/atf/atf-c/detail/fs_test
./usr/tests/atf/atf-c/detail/text_test
./usr/tests/atf/atf-c/detail/dynstr_test
./usr/tests/atf/atf-c/detail/sanity_test
./usr/tests/atf/atf-c/detail/list_test
./usr/tests/atf/atf-c/detail/user_test
./usr/tests/atf/atf-c/detail/process_helpers
./usr/tests/atf/atf-c/detail/map_test
./usr/tests/atf/atf-c++
./usr/tests/atf/atf-c++/atf_c++_test
./usr/tests/atf/atf-c++/macros_hpp_test.cpp
./usr/tests/atf/atf-c++/Kyuafile
./usr/tests/atf/atf-c++/tests_test
./usr/tests/atf/atf-c++/macros_test
./usr/tests/atf/atf-c++/build_test
./usr/tests/atf/atf-c++/check_test
./usr/tests/atf/atf-c++/utils_test
./usr/tests/atf/atf-c++/pkg_config_test
./usr/tests/atf/atf-c++/unused_test.cpp
./usr/tests/atf/atf-c++/detail
./usr/tests/atf/atf-c++/detail/version_helper
./usr/tests/atf/atf-c++/detail/env_test
./usr/tests/atf/atf-c++/detail/Kyuafile
./usr/tests/atf/atf-c++/detail/process_test
./usr/tests/atf/atf-c++/detail/exceptions_test
./usr/tests/atf/atf-c++/detail/fs_test
./usr/tests/atf/atf-c++/detail/application_test
./usr/tests/atf/atf-c++/detail/text_test
./usr/tests/atf/atf-c++/detail/auto_array_test
./usr/tests/atf/test-programs
./usr/tests/atf/test-programs/srcdir_test
./usr/tests/atf/test-programs/Kyuafile
./usr/tests/atf/test-programs/c_helpers
./usr/tests/atf/test-programs/sh_helpers
./usr/tests/atf/test-programs/expect_test
./usr/tests/atf/test-programs/config_test
./usr/tests/atf/test-programs/meta_data_test
./usr/tests/atf/test-programs/cpp_helpers
./usr/tests/atf/test-programs/result_test

Quoted 5 lines

Are all of these files needed on the target?

Thanks,

Thomas

************************************************************************************
This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************

Signature · 6 lines
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
#5 lore raw

PATCH v3 1/3 atf: new package

In reply to Sebastien Bourdelin

Dear Sebastien Bourdelin,

package/atf/atf.mk line 10

Quoted 4 lines · Sebastien Bourdelin
package/atf/atf.mk new file +4 -0
+ATF_VERSION = 0.21
+ATF_SITE = https://github.com/jmmv/atf/releases/download/atf-$(ATF_VERSION)
+ATF_INSTALL_STAGING = YES
+ATF_LICENSE = BSD-3c

The COPYING file actually has both BSD-2c and BSD-3c. Maybe specifying only BSD-3c is OK since it's the same as BSD-2c + an additional restriction. But I was just wondering what lead to mentioning only BSD-3c.

Thanks,

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
#6 lore raw

PATCH v3 1/3 atf: new package

Hi Thomas.

I do not know a lot about licenses, so it will be a lucky mistake if it's correct otherwise i can add the BSD-2c if you think it's required.

Thanks.

Quoted 16 lines · Thomas Petazzoni

Dear Sebastien Bourdelin,

package/atf/atf.mk line 10

Quoted 4 lines · Sebastien Bourdelin
package/atf/atf.mk new file +4 -0
+ATF_VERSION = 0.21
+ATF_SITE = https://github.com/jmmv/atf/releases/download/atf-$(ATF_VERSION)
+ATF_INSTALL_STAGING = YES
+ATF_LICENSE = BSD-3c

The COPYING file actually has both BSD-2c and BSD-3c. Maybe specifying only BSD-3c is OK since it's the same as BSD-2c + an additional restriction. But I was just wondering what lead to mentioning only BSD-3c.

Thanks,

Thomas

#7 lore raw

PATCH v3 1/3 atf: new package

Quoted 4 lines · Sebastien Bourdelin

Hi Thomas.

I do not know a lot about licenses, so it will be a lucky mistake if it's correct otherwise i can add the BSD-2c if you think it's required.

BSD-2c, BSD-3c is exactly what I suggested in my review of v1... But that was
probably not clear enough.

Regards,
Arnout

Quoted 32 lines

Thanks.

Quoted 13 lines · Thomas Petazzoni

Dear Sebastien Bourdelin,

package/atf/atf.mk line 10

Quoted 4 lines · Sebastien Bourdelin
package/atf/atf.mk new file +4 -0
+ATF_VERSION = 0.21
+ATF_SITE = https://github.com/jmmv/atf/releases/download/atf-$(ATF_VERSION)
+ATF_INSTALL_STAGING = YES
+ATF_LICENSE = BSD-3c

The COPYING file actually has both BSD-2c and BSD-3c. Maybe specifying only BSD-3c is OK since it's the same as BSD-2c + an additional restriction. But I was just wondering what lead to mentioning only BSD-3c.

Quoted 3 lines

Thanks,

Thomas

************************************************************************************
This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************

Signature · 6 lines
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
#8 lore raw

PATCH v3 1/3 atf: new package

Hi Arnout.

My mistake, i took it as a BSD-2c "or" BSD-3c.

I will fix that.

Thanks.

Quoted 42 lines · Arnout Vandecappelle
Quoted 4 lines · Sebastien Bourdelin

Hi Thomas.

I do not know a lot about licenses, so it will be a lucky mistake if it's correct otherwise i can add the BSD-2c if you think it's required.

BSD-2c, BSD-3c is exactly what I suggested in my review of v1... But that was
probably not clear enough.

Regards,
Arnout

Quoted 30 lines

Thanks.

Quoted 13 lines · Thomas Petazzoni

Dear Sebastien Bourdelin,

package/atf/atf.mk line 10

Quoted 4 lines · Sebastien Bourdelin
package/atf/atf.mk new file +4 -0
+ATF_VERSION = 0.21
+ATF_SITE = https://github.com/jmmv/atf/releases/download/atf-$(ATF_VERSION)
+ATF_INSTALL_STAGING = YES
+ATF_LICENSE = BSD-3c

The COPYING file actually has both BSD-2c and BSD-3c. Maybe specifying only BSD-3c is OK since it's the same as BSD-2c + an additional restriction. But I was just wondering what lead to mentioning only BSD-3c.

Quoted 3 lines

Thanks,

Thomas

************************************************************************************
This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************

#9 lore raw

PATCH v3 2/3 lutok: new package

In reply to Sebastien Bourdelin

Lutok is a lightweight C++ API library for Lua.

https://github.com/jmmv/lutok

---
Changes v2-> v3:
- rebase

suggested by Arnout Vandecapelle <[email protected]>:
- reworks comment in the Config.in for the required lua dependencies

Changes v1 -> v2:
suggested by Arnout Vandecapelle <[email protected]>:
- reworks lua dependencies, doesn't work with luajit
- adds comment in the Config.in for the required lua dependencies
- uses the release archive instead of the github automatic one
- updates the hash
- removes the useless AUTORECONF option
- adds optional dependency on atf
- don't generate the doxygen doc
- changes the license

---
 package/Config.in        |  1 +
 package/lutok/Config.in  | 13 +++++++++++++
 package/lutok/lutok.hash |  2 ++
 package/lutok/lutok.mk   | 26 ++++++++++++++++++++++++++
 4 files changed, 42 insertions(+)
 create mode 100644 package/lutok/Config.in
 create mode 100644 package/lutok/lutok.hash
 create mode 100644 package/lutok/lutok.mk
package/Config.in +1 -0
index 78ed223..628f36c 100644
@@ -457,6 +457,7 @@ endif
 	source "package/lua/Config.in"
 	source "package/luainterpreter/Config.in"
 	source "package/luajit/Config.in"
+	source "package/lutok/Config.in"
 if BR2_PACKAGE_HAS_LUAINTERPRETER && !BR2_STATIC_LIBS
 # lua modules are dynamically loaded, so not available on static builds
 menu "Lua libraries/modules"
package/lutok/Config.in new file +13 -0
new file mode 100644
index 0000000..ef885c8
@@ -0,0 +1,13 @@
+config BR2_PACKAGE_LUTOK
+	bool "lutok"
+	depends on BR2_INSTALL_LIBSTDCPP
+	depends on BR2_PACKAGE_HAS_LUAINTERPRETER \
+		&& !BR2_PACKAGE_LUAJIT
+	help
+	  Lutok is a lightweight C++ API library for Lua.
+
+	  https://github.com/jmmv/lutok
+
+comment "lutok needs a toolchain w/ C++ and full Lua"
+	depends on !BR2_INSTALL_LIBSTDCPP || BR2_PACKAGE_LUAJIT
+	depends on BR2_PACKAGE_HAS_LUAINTERPRETER
package/lutok/lutok.hash new file +2 -0
new file mode 100644
index 0000000..0ec8988
@@ -0,0 +1,2 @@
+# Locally computed
+sha256 2cec51efa0c8d65ace8b21eaa08384b77abc5087b46e785f78de1c21fb754cd5 lutok-0.4.tar.gz
package/lutok/lutok.mk new file +26 -0
new file mode 100644
index 0000000..0c78daa
@@ -0,0 +1,26 @@
+################################################################################
+#
+# lutok
+#
+################################################################################
+
+LUTOK_VERSION = 0.4
+LUTOK_SITE = https://github.com/jmmv/lutok/releases/download/lutok-$(LUTOK_VERSION)
+LUTOK_INSTALL_STAGING = YES
+LUTOK_DEPENDENCIES = host-pkgconf lua
+LUTOK_CONF_OPTS = --without-doxygen
+LUTOK_LICENSE = BSD-3c
+LUTOK_LICENSE_FILES = COPYING
+
+ifeq ($(BR2_PACKAGE_ATF),y)
+LUTOK_DEPENDENCIES += atf
+LUTOK_CONF_OPTS += --with-atf
+else
+LUTOK_CONF_OPTS += --without-atf
+endif
+
+ifneq ($(BR2_STATIC_LIBS),y)
+LUTOK_MAKE_OPTS = LIBS=-ldl
+endif
+
+$(eval $(autotools-package))
Signature · 1 line
2.4.0
#10 lore raw

PATCH v3 3/3 kyua: new package

In reply to Sebastien Bourdelin

Kyua is a testing framework for infrastructure software, originally designed to equip BSD-based operating systems with a test suite. This means that Kyua is lightweight and simple, and that Kyua integrates well with various build systems and continuous integration frameworks.

https://github.com/jmmv/kyua

---
Changes v2 -> v3:
- rebase

Changes v1 -> v2:
- don't generate the doxygen doc

suggested by Arnout Vandecapelle <[email protected]>:
- reworks dependencies in Config.in
- uses the uploaded archive instead of the github automatic one
- changes the hash
- removes the useless AUTORECONF
- changes the license
- fixes a mistake with POST_INSTALL_HOOK

---
 package/Config.in      |  1 +
 package/kyua/Config.in | 23 +++++++++++++++++++++++
 package/kyua/kyua.hash |  2 ++
 package/kyua/kyua.mk   | 27 +++++++++++++++++++++++++++
 4 files changed, 53 insertions(+)
 create mode 100644 package/kyua/Config.in
 create mode 100644 package/kyua/kyua.hash
 create mode 100644 package/kyua/kyua.mk
package/Config.in +1 -0
index 628f36c..3b2a886 100644
@@ -73,6 +73,7 @@ menu "Debugging, profiling and benchmark"
 	source "package/kexec/Config.in"
 	source "package/kexec-lite/Config.in"
 	source "package/ktap/Config.in"
+	source "package/kyua/Config.in"
 	source "package/latencytop/Config.in"
 	source "package/lmbench/Config.in"
 if BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
package/kyua/Config.in new file +23 -0
new file mode 100644
index 0000000..7489782
@@ -0,0 +1,23 @@
+config BR2_PACKAGE_KYUA
+	bool "kyua"
+	depends on BR2_INSTALL_LIBSTDCPP
+	depends on BR2_PACKAGE_HAS_LUAINTERPRETER \
+		&& !BR2_PACKAGE_LUAJIT # lutok
+	select BR2_PACKAGE_ATF
+	select BR2_PACKAGE_LUTOK
+	select BR2_PACKAGE_SQLITE
+	help
+	  Kyua is a testing framework for infrastructure software,
+	  originally designed to equip BSD-based operating systems
+	  with a test suite. This means that Kyua is lightweight
+	  and simple, and that Kyua integrates well with various build
+	  systems and continuous integration frameworks.
+
+	  https://github.com/jmmv/kyua
+
+comment "kyua needs a toolchain w/ C++"
+	depends on !BR2_INSTALL_LIBSTDCPP
+
+comment "kyua needs a Lua 5.1 interpreter or above"
+	depends on BR2_INSTALL_LIBSTDCPP && \
+		(!BR2_PACKAGE_HAS_LUAINTERPRETER || BR2_PACKAGE_LUAJIT)
package/kyua/kyua.hash new file +2 -0
new file mode 100644
index 0000000..938e556
@@ -0,0 +1,2 @@
+# Locally Calculted
+sha256 2b8b64a458b642df75086eeb73e8073d105b8d9cff04c9b1a905b68bc8502560 kyua-0.11.tar.gz
package/kyua/kyua.mk new file +27 -0
new file mode 100644
index 0000000..783d3db
@@ -0,0 +1,27 @@
+################################################################################
+#
+# kyua
+#
+################################################################################
+
+KYUA_VERSION = 0.11
+KYUA_SITE = https://github.com/jmmv/kyua/releases/download/kyua-$(KYUA_VERSION)
+KYUA_DEPENDENCIES = host-pkgconf atf lutok sqlite
+KYUA_CONF_OPTS = --without-doxygen
+KYUA_LICENSE = BSD-3c
+KYUA_LICENSE_FILES = COPYING
+KYUA_CONF_ENV = \
+	kyua_cv_attribute_noreturn=yes \
+	kyua_cv_getcwd_dyn=yes \
+	kyua_cv_lchmod_works=no \
+	kyua_cv_getopt_gnu=yes \
+	kyua_cv_getopt_optind_reset_value=0 \
+	kyua_cv_signals_lastno=15
+
+define KYUA_INSTALL_CONFIG
+	$(INSTALL) -D -m 644 $(@D)/examples/kyua.conf $(TARGET_DIR)/etc/kyua/kyua.conf
+endef
+
+KYUA_POST_INSTALL_HOOKS += KYUA_INSTALL_CONFIG
+
+$(eval $(autotools-package))
Signature · 1 line
2.4.0