Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 5/7] package/nodejs: remove version choice
Date: Wed, 30 Dec 2015 01:09:00 +0100	[thread overview]
Message-ID: <5683209C.2060001@mind.be> (raw)
In-Reply-To: <CAFGQKxde_+aNen+tipZq8k=Nd+ErNHBY6YJQeOD7GGQQ1vX57g@mail.gmail.com>

On 24-12-15 17:23, Martin Bark wrote:
> Thomas,
> 
> On 23 December 2015 at 17:56, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> Martin,
>>
>> On Wed, 23 Dec 2015 12:16:06 +0000, Martin Bark wrote:
>>
>>> diff --git a/package/nodejs/Config.in b/package/nodejs/Config.in
>>> index eb3aeec..1aac38e 100644
>>> --- a/package/nodejs/Config.in
>>> +++ b/package/nodejs/Config.in
>>> @@ -6,6 +6,7 @@ config BR2_PACKAGE_NODEJS
>>>       depends on !BR2_MIPS_SOFT_FLOAT
>>>       # ARM needs BLX, so v5t+
>>>       depends on !BR2_ARM_CPU_ARMV4
>>> +     depends on BR2_PACKAGE_NODEJS_0_10_X || BR2_PACKAGE_NODEJS_5_X
>>
>> I don't like that the main BR2_PACKAGE_NODEJS option depends on
>> BR2_PACKAGE_NODEJS_0_10_X || BR2_PACKAGE_NODEJS_5_X.
>>
>> Instead, please do something like:
>>
>> BR2_PACKAGE_NODEJS_VERSION
>>         string
>>         default "5.3.0"   if BR2_PACKAGE_NODEJS_V8_ARCH_SUPPORTS && BR2_TOOLCHAIN_GCC_AT_LEAST_4_8 && BR2_USE_WCHAR
>>         default "0.10.41"
>>
>> And then use BR2_PACKAGE_NODEJS_VERSION in nodejs.mk to find which
>> version to use.
> 
> I'm not 100% clear what you want.  If BR2_PACKAGE_NODEJS does not
> depend on BR2_PACKAGE_NODEJS_0_10_X || BR2_PACKAGE_NODEJS_5_X then you
> can select nodejs when some dependencies are not satisfied.

 No, because BR2_PACKAGE_NODEJS already has the required depends on
!BR2_ARM_CPU_ARMV4 and others, so this is not an issue.


> This
> would mean 0.10.x would get installed on architectures other than
> armv5.  I thought the idea was 0.10.x only on armv5.  Can you please
> clarify.

 No it doesn't, with Thomas's proposal, 5.3.0 will be selected except if it is
not supported.


 By the way, if/when you repost, please include the host-gcc version check
patches that I just sent, because they are conflicting.

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2015-12-30  0:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-23 12:16 [Buildroot] [PATCH v3 1/7] package/nodejs: bump version to 5.3.0 Martin Bark
2015-12-23 12:16 ` [Buildroot] [PATCH v3 2/7] package/nodejs: removed version 0.12.9 Martin Bark
2015-12-23 12:16 ` [Buildroot] [PATCH v3 3/7] package/nodejs: correct 0.10.x option name Martin Bark
2015-12-23 12:16 ` [Buildroot] [PATCH v3 4/7] package/nodejs: fixed comment for mips soft float Martin Bark
2015-12-23 12:16 ` [Buildroot] [PATCH v3 5/7] package/nodejs: remove version choice Martin Bark
2015-12-23 17:56   ` Thomas Petazzoni
2015-12-23 18:26     ` Yann E. MORIN
2015-12-24 16:23     ` Martin Bark
2015-12-30  0:09       ` Arnout Vandecappelle [this message]
2015-12-23 12:16 ` [Buildroot] [PATCH v3 6/7] package/nodejs: fix support for uClibc-ng Martin Bark
2015-12-23 12:16 ` [Buildroot] [PATCH v3 7/7] package/libuv: " Martin Bark
2015-12-23 17:54 ` [Buildroot] [PATCH v3 1/7] package/nodejs: bump version to 5.3.0 Thomas Petazzoni
2015-12-24 16:16   ` Martin Bark
2015-12-25 17:49     ` Thomas Petazzoni

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=5683209C.2060001@mind.be \
    --to=arnout@mind.be \
    --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