From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd.kuhls@t-online.de>
Cc: Samuel Martin <s.martin49@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/4] package/dht: new package
Date: Mon, 1 Aug 2022 22:10:51 +0200 [thread overview]
Message-ID: <20220801221051.5c864a38@windsurf> (raw)
In-Reply-To: <20220727181304.440002-3-bernd.kuhls@t-online.de>
On Wed, 27 Jul 2022 20:13:03 +0200
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> Needed for upcoming version bump of transmission.
>
> Build test using this defconfig
>
> BR2_PACKAGE_DHT=y
I was not really happy with the patch adding CMakeLists.txt that
upstream rejected. But the upstream Makefile does not even allow
building dht as a library, nor installing its header file. So the other
option would have been to do it directly in the Buildroot .mk file,
which is not really better than adding a CMakeLists.txt. So I've
applied as-is, even if it's not ideal.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-01 20:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 18:13 [Buildroot] [PATCH 1/4] package/libutp: bump version Bernd Kuhls
2022-07-27 18:13 ` [Buildroot] [PATCH 2/4] package/libdeflate: new package Bernd Kuhls
2022-08-01 20:09 ` Thomas Petazzoni via buildroot
2022-07-27 18:13 ` [Buildroot] [PATCH 3/4] package/dht: " Bernd Kuhls
2022-08-01 20:10 ` Thomas Petazzoni via buildroot [this message]
2022-07-27 18:13 ` [Buildroot] [PATCH/RFC 4/4] package/transmission: bump version Bernd Kuhls
2022-08-01 20:09 ` [Buildroot] [PATCH 1/4] package/libutp: " Thomas Petazzoni via buildroot
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=20220801221051.5c864a38@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd.kuhls@t-online.de \
--cc=s.martin49@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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