Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/cmake: bump version to 3.10.0 and add license hash
Date: Tue, 19 Dec 2017 09:39:47 +0100	[thread overview]
Message-ID: <20171219093947.7256a9c2@windsurf> (raw)
In-Reply-To: <87ind37kdt.fsf@dell.be.48ers.dk>

Hello,

On Mon, 18 Dec 2017 23:15:42 +0100, Peter Korsgaard wrote:

>  > I looke at my autobuilder, and it uses gcc-4.8.2, and cmake builds fine
>  > with that...  
> 
>  > gcc-4.8 was released in March 2013, which will be almost 5 years ago
>  > when we tag LTS 2018.02. So maybe we can keep using cmake-3.9 up until
>  > 2018.02, then update our requirements to require a host gcc >= 4.8m
>  > which will allow us to bump cmake to 3.10.  
> 
>  > I agree that, with time passing, more and more packages will require
>  > C++11, so it will make sense to require proper C++11 support for the
>  > host compiler.  
> 
> Yes, maybe that is indeed the best way forward - Post 2018.02 that is.

It feels a bit annoying to make such a change that would impact all
Buildroot users, just for the sole reason of an optimization down into
CMake.

I agree that we won't be able to avoid using a C++11 compiler on the
host at some point. I'm just trying to see if we can avoid this when
reasonably possible.

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

      reply	other threads:[~2017-12-19  8:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-10 23:33 [Buildroot] [PATCH] package/cmake: bump version to 3.10.0 and add license hash Mario Lang
2017-12-12  6:07 ` Thomas Petazzoni
2017-12-12 11:30   ` Thomas Petazzoni
2017-12-16 10:52     ` Mario Lang
2017-12-16 10:52       ` [Buildroot] FW: " Kees van Unen
2017-12-16 12:34       ` [Buildroot] " Thomas Petazzoni
2017-12-17 17:39         ` Yann E. MORIN
2017-12-18 22:15           ` Peter Korsgaard
2017-12-19  8:39             ` Thomas Petazzoni [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=20171219093947.7256a9c2@windsurf \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox