From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libftdi1: fix swig build error when using cmake 3.12
Date: Wed, 26 Dec 2018 22:30:48 +0100 [thread overview]
Message-ID: <20181226213048.GJ14286@scaer> (raw)
In-Reply-To: <20181226221840.0181c8ec@windsurf>
Thomas, All,
On 2018-12-26 22:18 +0100, Thomas Petazzoni spake thusly:
> On Sun, 23 Dec 2018 22:29:23 +0100, Yann E. MORIN wrote:
> > We've another user on IRC, reporting issues with cmake-3.13. Should we
> > now black=list cmake 3.12 and above, and always build our own?
>
> I really don't like blacklisting recent versions of tools. So if we
> were to blacklist CMake 3.13 and newer, I'd like to see a proper
> explanation of what the problem is and why blacklisting CMake 3.13 and
> newer is the only reasonable solution.
100% agreed.
Let's put this at rest until we have proper explanation and reproducer.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-12-26 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 19:57 [Buildroot] [PATCH 1/1] package/libftdi1: fix swig build error when using cmake 3.12 Mark Corbin
2018-12-23 21:29 ` Yann E. MORIN
2018-12-26 21:18 ` Thomas Petazzoni
2018-12-26 21:30 ` Yann E. MORIN [this message]
2018-12-26 21:17 ` Thomas Petazzoni
2019-01-18 13:03 ` Peter Korsgaard
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=20181226213048.GJ14286@scaer \
--to=yann.morin.1998@free.fr \
--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