[Buildroot] [PATCH v3 0/3] kyua: new package and dependencies

Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed

* [Buildroot] [PATCH v3 0/3] kyua: new package and dependencies
@ 2015-06-07 22:55 Sebastien Bourdelin
  2015-06-07 22:55 ` [Buildroot] [PATCH v3 1/3] atf: new package Sebastien Bourdelin
                   ` (2 more replies)
  0 siblings, 3 replies; 11+ messages in thread
From: Sebastien Bourdelin @ 2015-06-07 22:55 UTC (permalink / raw)
  To: buildroot

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

-- 
2.4.0

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Buildroot] [PATCH v3 1/3] atf: new package
  2015-06-07 22:55 [Buildroot] [PATCH v3 0/3] kyua: new package and dependencies Sebastien Bourdelin
@ 2015-06-07 22:55 ` Sebastien Bourdelin
  2015-06-11 20:33   ` Thomas Petazzoni
  2015-06-11 20:34   ` Thomas Petazzoni
  2015-06-07 22:55 ` [Buildroot] [PATCH v3 2/3] lutok: " Sebastien Bourdelin
  2015-06-07 22:55 ` [Buildroot] [PATCH v3 3/3] kyua: " Sebastien Bourdelin
  2 siblings, 2 replies; 11+ messages in thread
From: Sebastien Bourdelin @ 2015-06-07 22:55 UTC (permalink / raw)
  To: buildroot

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

Signed-off-by: Sebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com>
---
Changes v2 -> v3:
  - rebase

  suggested by Arnout Vandecapelle <arnout@mind.be>:
  - adds comment to explain the need to use AUTORECONF

Changes v1 -> v2:
  suggested by Arnout Vandecapelle <arnout@mind.be>:
  - 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

diff --git a/package/Config.in b/package/Config.in
index e0c2e2a..78ed223 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -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"
diff --git a/package/atf/Config.in b/package/atf/Config.in
new file mode 100644
index 0000000..59712ab
--- /dev/null
+++ b/package/atf/Config.in
@@ -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
diff --git a/package/atf/atf.hash b/package/atf/atf.hash
new file mode 100644
index 0000000..78cd3c6
--- /dev/null
+++ b/package/atf/atf.hash
@@ -0,0 +1,2 @@
+# Locally computed
+sha256 92bc64180135eea8fe84c91c9f894e678767764f6dbc8482021d4dde09857505 atf-0.21.tar.gz
diff --git a/package/atf/atf.mk b/package/atf/atf.mk
new file mode 100644
index 0000000..bf6f156
--- /dev/null
+++ b/package/atf/atf.mk
@@ -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))
-- 
2.4.0

^ permalink raw reply related	[flat|nested] 11+ messages in thread

* [Buildroot] [PATCH v3 1/3] atf: new package
  2015-06-07 22:55 ` [Buildroot] [PATCH v3 1/3] atf: new package Sebastien Bourdelin
@ 2015-06-11 20:33   ` Thomas Petazzoni
  2015-06-11 20:42     ` Sebastien Bourdelin
  2015-06-11 20:34   ` Thomas Petazzoni
  1 sibling, 1 reply; 11+ messages in thread
From: Thomas Petazzoni @ 2015-06-11 20:33 UTC (permalink / raw)
  To: buildroot

Dear Sebastien Bourdelin,

On Sun,  7 Jun 2015 18:55:25 -0400, Sebastien Bourdelin wrote:

>  menu "Debugging, profiling and benchmark"
> +	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?

> new file mode 100644
> index 0000000..bf6f156
> --- /dev/null
> +++ b/package/atf/atf.mk
> @@ -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))

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
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Buildroot] [PATCH v3 1/3] atf: new package
  2015-06-11 20:33   ` Thomas Petazzoni
@ 2015-06-11 20:42     ` Sebastien Bourdelin
  2015-06-11 21:06       ` Arnout Vandecappelle
  0 siblings, 1 reply; 11+ messages in thread
From: Sebastien Bourdelin @ 2015-06-11 20:42 UTC (permalink / raw)
  To: buildroot

Hi Thomas.

I will leave you that choice :)

Thanks.

On 06/11/2015 04:33 PM, Thomas Petazzoni wrote:
> Dear Sebastien Bourdelin,
>
> On Sun,  7 Jun 2015 18:55:25 -0400, Sebastien Bourdelin wrote:
>
>>  menu "Debugging, profiling and benchmark"
>> +	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?
>
>> new file mode 100644
>> index 0000000..bf6f156
>> --- /dev/null
>> +++ b/package/atf/atf.mk
>> @@ -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))
> 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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Buildroot] [PATCH v3 1/3] atf: new package
  2015-06-11 20:42     ` Sebastien Bourdelin
@ 2015-06-11 21:06       ` Arnout Vandecappelle
  0 siblings, 0 replies; 11+ messages in thread
From: Arnout Vandecappelle @ 2015-06-11 21:06 UTC (permalink / raw)
  To: buildroot

On 06/11/15 22:42, Sebastien Bourdelin wrote:
> Hi Thomas.
> 
> I will leave you that choice :)
> 
> Thanks.
> 
> On 06/11/2015 04:33 PM, Thomas Petazzoni wrote:
[snip]
>> 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

>>
>> ./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
> 
> 
>  
>  
> ************************************************************************************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
> ************************************************************************************
> 
> 
> 
> 


-- 
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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Buildroot] [PATCH v3 1/3] atf: new package
  2015-06-07 22:55 ` [Buildroot] [PATCH v3 1/3] atf: new package Sebastien Bourdelin
  2015-06-11 20:33   ` Thomas Petazzoni
@ 2015-06-11 20:34   ` Thomas Petazzoni
  2015-06-11 20:41     ` Sebastien Bourdelin
  1 sibling, 1 reply; 11+ messages in thread
From: Thomas Petazzoni @ 2015-06-11 20:34 UTC (permalink / raw)
  To: buildroot

Dear Sebastien Bourdelin,

On Sun,  7 Jun 2015 18:55:25 -0400, Sebastien Bourdelin wrote:

> +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
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Buildroot] [PATCH v3 1/3] atf: new package
  2015-06-11 20:34   ` Thomas Petazzoni
@ 2015-06-11 20:41     ` Sebastien Bourdelin
  2015-06-11 20:45       ` Arnout Vandecappelle
  0 siblings, 1 reply; 11+ messages in thread
From: Sebastien Bourdelin @ 2015-06-11 20:41 UTC (permalink / raw)
  To: buildroot

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.

On 06/11/2015 04:34 PM, Thomas Petazzoni wrote:
> Dear Sebastien Bourdelin,
>
> On Sun,  7 Jun 2015 18:55:25 -0400, Sebastien Bourdelin wrote:
>
>> +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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Buildroot] [PATCH v3 1/3] atf: new package
  2015-06-11 20:41     ` Sebastien Bourdelin
@ 2015-06-11 20:45       ` Arnout Vandecappelle
  2015-06-11 20:48         ` Sebastien Bourdelin
  0 siblings, 1 reply; 11+ messages in thread
From: Arnout Vandecappelle @ 2015-06-11 20:45 UTC (permalink / raw)
  To: buildroot

On 06/11/15 22:41, Sebastien Bourdelin wrote:
> 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

> 
> Thanks.
> 
> On 06/11/2015 04:34 PM, Thomas Petazzoni wrote:
>> Dear Sebastien Bourdelin,
>>
>> On Sun,  7 Jun 2015 18:55:25 -0400, Sebastien Bourdelin wrote:
>>
>>> +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
> 
> 
>  
>  
> ************************************************************************************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
> ************************************************************************************
> 
> 
> 
> 


-- 
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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Buildroot] [PATCH v3 1/3] atf: new package
  2015-06-11 20:45       ` Arnout Vandecappelle
@ 2015-06-11 20:48         ` Sebastien Bourdelin
  0 siblings, 0 replies; 11+ messages in thread
From: Sebastien Bourdelin @ 2015-06-11 20:48 UTC (permalink / raw)
  To: buildroot

Hi Arnout.

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

I will fix that.

Thanks.

On 06/11/2015 04:45 PM, Arnout Vandecappelle wrote:
> On 06/11/15 22:41, Sebastien Bourdelin wrote:
>> 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
>
>> Thanks.
>>
>> On 06/11/2015 04:34 PM, Thomas Petazzoni wrote:
>>> Dear Sebastien Bourdelin,
>>>
>>> On Sun,  7 Jun 2015 18:55:25 -0400, Sebastien Bourdelin wrote:
>>>
>>>> +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
>>
>>  
>>  
>> ************************************************************************************
>> This footnote confirms that this email message has been scanned by
>> PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
>> ************************************************************************************
>>
>>
>>
>>
>

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Buildroot] [PATCH v3 2/3] lutok: new package
  2015-06-07 22:55 [Buildroot] [PATCH v3 0/3] kyua: new package and dependencies Sebastien Bourdelin
  2015-06-07 22:55 ` [Buildroot] [PATCH v3 1/3] atf: new package Sebastien Bourdelin
@ 2015-06-07 22:55 ` Sebastien Bourdelin
  2015-06-07 22:55 ` [Buildroot] [PATCH v3 3/3] kyua: " Sebastien Bourdelin
  2 siblings, 0 replies; 11+ messages in thread
From: Sebastien Bourdelin @ 2015-06-07 22:55 UTC (permalink / raw)
  To: buildroot

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

https://github.com/jmmv/lutok

Signed-off-by: Sebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com>
---
Changes v2-> v3:
  - rebase

  suggested by Arnout Vandecapelle <arnout@mind.be>:
  - reworks comment in the Config.in for the required lua dependencies

Changes v1 -> v2:
  suggested by Arnout Vandecapelle <arnout@mind.be>:
  - 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

diff --git a/package/Config.in b/package/Config.in
index 78ed223..628f36c 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -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"
diff --git a/package/lutok/Config.in b/package/lutok/Config.in
new file mode 100644
index 0000000..ef885c8
--- /dev/null
+++ b/package/lutok/Config.in
@@ -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
diff --git a/package/lutok/lutok.hash b/package/lutok/lutok.hash
new file mode 100644
index 0000000..0ec8988
--- /dev/null
+++ b/package/lutok/lutok.hash
@@ -0,0 +1,2 @@
+# Locally computed
+sha256 2cec51efa0c8d65ace8b21eaa08384b77abc5087b46e785f78de1c21fb754cd5 lutok-0.4.tar.gz
diff --git a/package/lutok/lutok.mk b/package/lutok/lutok.mk
new file mode 100644
index 0000000..0c78daa
--- /dev/null
+++ b/package/lutok/lutok.mk
@@ -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))
-- 
2.4.0

^ permalink raw reply related	[flat|nested] 11+ messages in thread

* [Buildroot] [PATCH v3 3/3] kyua: new package
  2015-06-07 22:55 [Buildroot] [PATCH v3 0/3] kyua: new package and dependencies Sebastien Bourdelin
  2015-06-07 22:55 ` [Buildroot] [PATCH v3 1/3] atf: new package Sebastien Bourdelin
  2015-06-07 22:55 ` [Buildroot] [PATCH v3 2/3] lutok: " Sebastien Bourdelin
@ 2015-06-07 22:55 ` Sebastien Bourdelin
  2 siblings, 0 replies; 11+ messages in thread
From: Sebastien Bourdelin @ 2015-06-07 22:55 UTC (permalink / raw)
  To: buildroot

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

Signed-off-by: Sebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com>
---
Changes v2 -> v3:
  - rebase

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

  suggested by Arnout Vandecapelle <arnout@mind.be>:
  - 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

diff --git a/package/Config.in b/package/Config.in
index 628f36c..3b2a886 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -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
diff --git a/package/kyua/Config.in b/package/kyua/Config.in
new file mode 100644
index 0000000..7489782
--- /dev/null
+++ b/package/kyua/Config.in
@@ -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)
diff --git a/package/kyua/kyua.hash b/package/kyua/kyua.hash
new file mode 100644
index 0000000..938e556
--- /dev/null
+++ b/package/kyua/kyua.hash
@@ -0,0 +1,2 @@
+# Locally Calculted
+sha256 2b8b64a458b642df75086eeb73e8073d105b8d9cff04c9b1a905b68bc8502560 kyua-0.11.tar.gz
diff --git a/package/kyua/kyua.mk b/package/kyua/kyua.mk
new file mode 100644
index 0000000..783d3db
--- /dev/null
+++ b/package/kyua/kyua.mk
@@ -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))
-- 
2.4.0

^ permalink raw reply related	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2015-06-11 21:06 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-06-07 22:55 [Buildroot] [PATCH v3 0/3] kyua: new package and dependencies Sebastien Bourdelin
2015-06-07 22:55 ` [Buildroot] [PATCH v3 1/3] atf: new package Sebastien Bourdelin
2015-06-11 20:33   ` Thomas Petazzoni
2015-06-11 20:42     ` Sebastien Bourdelin
2015-06-11 21:06       ` Arnout Vandecappelle
2015-06-11 20:34   ` Thomas Petazzoni
2015-06-11 20:41     ` Sebastien Bourdelin
2015-06-11 20:45       ` Arnout Vandecappelle
2015-06-11 20:48         ` Sebastien Bourdelin
2015-06-07 22:55 ` [Buildroot] [PATCH v3 2/3] lutok: " Sebastien Bourdelin
2015-06-07 22:55 ` [Buildroot] [PATCH v3 3/3] kyua: " Sebastien Bourdelin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox