All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Perez de Castro <aperez@igalia.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] pkg-cmake.mk: Set CMAKE_SYSTEM_PROCESSOR_ARM_VARIANT for ARMv8
Date: Thu, 6 Jul 2017 12:14:46 +0300	[thread overview]
Message-ID: <20170706121446.GC21278@momiji> (raw)
In-Reply-To: <407724d9-6ae3-b166-63df-7d1559d2160c@mind.be>

Hi Arnout,

Thanks for the reviewing :-)

On Wed, 5 Jul 2017 22:23:26 +0200, Arnout Vandecappelle <arnout@mind.be> wrote:

> On 05-07-17 21:08, Adrian Perez de Castro wrote:
> > This is needed for correctly building some CMake-based packages which
> > use this variable. For example, this is needed for WebKitGTK+ 2.16.x
> > to build correctly when an ARMv8 target is configured.
> 
>  Well, it's needed for any cmake package on ARMv8...
> 
> 
> > Signed-off-by: Adrian Perez de Castro <aperez@igalia.com>
> 
> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> 
> > ---
> >  package/pkg-cmake.mk | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > diff --git a/package/pkg-cmake.mk b/package/pkg-cmake.mk
> > index 401084fb12..914bda7482 100644
> > --- a/package/pkg-cmake.mk
> > +++ b/package/pkg-cmake.mk
> > @@ -219,6 +219,8 @@ else ifeq ($(BR2_ARM_CPU_ARMV6),y)
> >  CMAKE_SYSTEM_PROCESSOR_ARM_VARIANT = armv6
> >  else ifeq ($(BR2_ARM_CPU_ARMV7A),y)
> 
>  I noticed that armv7m is also missing. Could you try to find the corresponding
> CMake architecture and add it?

Sure, I'll try and look into this.

>  Also, it could be useful to add
> 
> else
> $(error ARM CPU variant not set for CMake)
> endif
> 
>  Not *that* helpful for users, but better than the error you got :-)

I think that is a good idea. Even if for an user it is not so handy, it is
better to fail early. It took me a good while to figure out where was the root
of the issue was, and having an error message early would have been faster.
Even if a build succeeds without setting CMAKE_SYSTEM_PROCESSOR_ARM_VARIANT,
not having a correct value here could potentially cause mysterious failures at
run-time. I'll be sending a patch for this later as well.

Cheers,

--
 Adri?n ?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170706/4d9a046e/attachment.asc>

  reply	other threads:[~2017-07-06  9:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 19:08 [Buildroot] [PATCH 0/1] Fix for packages which use CMAKE_SYSTEM_PROCESSOR_ARM_VARIANT and target is ARMv8 Adrian Perez de Castro
2017-07-05 19:08 ` [Buildroot] [PATCH 1/1] pkg-cmake.mk: Set CMAKE_SYSTEM_PROCESSOR_ARM_VARIANT for ARMv8 Adrian Perez de Castro
2017-07-05 20:23   ` Arnout Vandecappelle
2017-07-06  9:14     ` Adrian Perez de Castro [this message]
2017-07-06 21:24   ` Thomas Petazzoni
2017-07-06 21:27     ` Adrian Perez de Castro

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=20170706121446.GC21278@momiji \
    --to=aperez@igalia.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.