All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [V2 2/2] ljlinenoise: new package
Date: Mon, 3 Feb 2014 22:56:08 +0100	[thread overview]
Message-ID: <20140203225608.4593b632@skate> (raw)
In-Reply-To: <20140203202630.GB3264@free.fr>

Dear Yann E. MORIN,

On Mon, 3 Feb 2014 21:26:31 +0100, Yann E. MORIN wrote:

> > diff --git a/package/ljlinenoise/Config.in b/package/ljlinenoise/Config.in
> > new file mode 100644
> > index 0000000..3d2af35
> > --- /dev/null
> > +++ b/package/ljlinenoise/Config.in
> > @@ -0,0 +1,15 @@
> > +config BR2_PACKAGE_LJLINENOISE
> > +	bool "ljlinenoise"
> > +	select BR2_PACKAGE_LJSYSCALL
> > +	# ljsyscall is specifically for LuaJIT, not Lua.
> > +	depends on BR2_PACKAGE_LUAJIT
> > +	# ljsyscall is only available for some target architectures
> > +	depends on BR2_i386 || BR2_x86_64 || BR2_powerpc || BR2_arm || BR2_armeb
> 
> No need for the comment, it is obvious from the dependency itself that
> ljlinenoise only works on these architectures.

Hum, really? These dependencies are inherited from ljsyscall, which is
selected by this package. In such a situation, we normally do something
like:

	select BR2_PACKAGE_LIBGLIB2
	depends on BR2_USE_WCHAR # libglib2

so having the same comment mentioned here makes sense, IMO, as it helps
understanding where the architecture dependency is coming from.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-02-03 21:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 11:07 [Buildroot] [V2 1/2] luarocks: never wraps script Francois Perrad
2014-02-03 11:07 ` [Buildroot] [V2 2/2] ljlinenoise: new package Francois Perrad
2014-02-03 20:26   ` Yann E. MORIN
2014-02-03 21:56     ` Thomas Petazzoni [this message]
2014-02-03 22:04       ` Yann E. MORIN
2014-02-03 20:16 ` [Buildroot] [V2 1/2] luarocks: never wraps script Yann E. MORIN

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=20140203225608.4593b632@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.