From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/1] package/xmrig: new package
Date: Mon, 24 May 2021 14:00:04 +0200 [thread overview]
Message-ID: <20210524120004.GP3208066@scaer> (raw)
In-Reply-To: <20210523103047.595306-1-bernd.kuhls@t-online.de>
Bernd, All,
On 2021-05-23 12:30 +0200, Bernd Kuhls spake thusly:
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
[--SNIP--]
> diff --git a/package/xmrig/Config.in b/package/xmrig/Config.in
> new file mode 100644
> index 0000000000..3007201610
> --- /dev/null
> +++ b/package/xmrig/Config.in
> @@ -0,0 +1,22 @@
> +config BR2_PACKAGE_XMRIG
> + bool "xmrig"
> + # archs officially supported by upstream
> + depends on BR2_aarch64 || BR2_x86_64 || BR2_i386
> + depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL # libuv
> + depends on BR2_USE_MMU # libuv
MMU is an architecture dependency, it moust come before toolchain
dependencies.
> + depends on !BR2_STATIC_LIBS # libuv
> + depends on BR2_TOOLCHAIN_HAS_SYNC_4 # libuv
> + # xmrig needs fenv.h which is not provided by uclibc
> + depends on !BR2_TOOLCHAIN_USES_UCLIBC
> + select BR2_PACKAGE_LIBUV
> + help
> + RandomX, CryptoNight, AstroBWT and Argon2 CPU/GPU miner.
> +
> + https://xmrig.com
> +
> +comment "xmrig needs a glibc or musl toolchain w/ NPTL, dynamic library"
> + depends on BR2_TOOLCHAIN_USES_UCLIBC || \
> + !BR2_TOOLCHAIN_HAS_THREADS_NPTL || BR2_STATIC_LIBS
> + depends on BR2_aarch64 || BR2_x86_64 || BR2_i386
> + depends on BR2_USE_MMU
> + depends on BR2_TOOLCHAIN_HAS_SYNC_4
Keep the same ordering in the comment depndencies as in the main option
dependencies.
[--SNIP--]
> diff --git a/package/xmrig/xmrig.mk b/package/xmrig/xmrig.mk
> new file mode 100644
> index 0000000000..aa36fcdf57
> --- /dev/null
> +++ b/package/xmrig/xmrig.mk
> @@ -0,0 +1,40 @@
[--SNIP--]
> +define XMRIG_INSTALL_TARGET_CMDS
> + $(INSTALL) -m 0755 -D $(@D)/xmrig$(if $(BR2_PACKAGE_OPENSSL),,-notls) \
> + $(TARGET_DIR)/usr/bin/xmrig$(if $(BR2_PACKAGE_OPENSSL),,-notls)
> +endef
Why can't we use the default install commands?
Regards,
Yann E. MORIN.
> +
> +$(eval $(cmake-package))
> --
> 2.29.2
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2021-05-24 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 10:30 [Buildroot] [PATCH/next 1/1] package/xmrig: new package Bernd Kuhls
2021-05-24 12:00 ` Yann E. MORIN [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210524120004.GP3208066@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox