From 40d5bf64408a0e103f8149f941ea50fbbb11dc91 Mon Sep 17 00:00:00 2001 From: Alexey Neyman Date: Fri, 23 Nov 2018 22:14:07 -0800 Subject: Add moxiebox as a choice for libc This required some rework of the libc selection, as moxiebox is a layer on top of another libc - newlib. Also, moxiebox'es host VM (`sandbox`) needs a libcrypto on the host. We will not have it if we're cross-compiling a canadian cross. Fortunately, all moxiebox needs from libcrypto is SHA256, and it already includes a standalone implementation of SHA256 in its runtime. Provide a little wrapper that allows moxiebox use that implementation for the host binary, too. Also, automate collecting/printing the list of all packages in a given category (e.g. LIBC or COMP_TOOLS), generate a list of all Kconfig symbols for a given category. Signed-off-by: Alexey Neyman --- samples/moxie-unknown-moxiebox/crosstool.config | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 samples/moxie-unknown-moxiebox/crosstool.config (limited to 'samples/moxie-unknown-moxiebox/crosstool.config') diff --git a/samples/moxie-unknown-moxiebox/crosstool.config b/samples/moxie-unknown-moxiebox/crosstool.config new file mode 100644 index 00000000..6fae8592 --- /dev/null +++ b/samples/moxie-unknown-moxiebox/crosstool.config @@ -0,0 +1,6 @@ +CT_EXPERIMENTAL=y +CT_ARCH_MOXIE=y +CT_DEBUG_GDB=y +CT_GDB_CROSS_SIM=y +# CT_GDB_CROSS_PYTHON is not set +CT_DTC_VERBOSE=y -- cgit v1.2.3