From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7 1/1] package/swupdate: new package
Date: Fri, 31 Jul 2015 22:14:21 +0200 [thread overview]
Message-ID: <1438373661.26917.11.camel@embedded.rocks> (raw)
In-Reply-To: <55B7B009.1080202@openwide.fr>
On Di, 2015-07-28 at 18:38 +0200, Romain Naour wrote:
> Hi J?rg,
[snip]
> Can you check for toolchain dependencies ?
>
> swupdate seems depends on BR2_TOOLCHAIN_HAS_THREADS since pthread functions are
> used all over the place.
>
> Also, when mongoose web server is enable swupdate must also depends
> on BR2_USE_MMU.
> I don't know if swupdate can really be used in a mmu less system, so
> it's ok if
> swupdate depends on BR2_USE_MMU even when mongoose support is
> disabled.
You're right! I'll add those dependencies.
[snip]
> Some days after your sent this patch, the 2015.07 release has been
> tagged in the
> repository. It's only 3 commits after this one.
I'll update to this version.
[snip]
> It not obvious that you must enable CONFIG_DOWNLOAD in
> swupdate
> config to use
> libcurl. I don't know how to express this dependency, so a comment is
> welcome here.
Actually, you've to select libcurl first to be able to enable
CONFIG_DOWNLOAD. A comment about this is in the help text.
> Have you tried to use $(call
> KCONFIG_ENABLE_OPT,CONFIG_DOWNLOAD,$(@D)/.config)
> in KCONFIG_FIXUP_CMDS ?
I followed Arnouts suggestion [1] to remove all the user options that
update the .config file as the user can just make swupdate-menuconfig.
The help text tells the user which other packages may be of interest.
> Sorry for the late review.
Never mind! Thanks for the review!
[1]
http://patchwork.ozlabs.org/patch/451763/
next prev parent reply other threads:[~2015-07-31 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 19:22 [Buildroot] [PATCH v7 1/1] package/swupdate: new package Jörg Krause
2015-07-28 16:38 ` Romain Naour
2015-07-31 20:14 ` Jörg Krause [this message]
2015-07-31 21:33 ` Romain Naour
2015-08-01 6:37 ` Jörg Krause
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=1438373661.26917.11.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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