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] kmsxx: not available on m68k
Date: Tue, 14 Feb 2017 12:58:37 +0100	[thread overview]
Message-ID: <20170214125837.69821038@free-electrons.com> (raw)
In-Reply-To: <20170214114204.GD12810@waldemar-brodkorb.de>

Hello,

On Tue, 14 Feb 2017 12:42:04 +0100, Waldemar Brodkorb wrote:

> I can try. But now I am back to my original problem, how do I
> overwrite CFLAGS/CXXFLAGS correctly for a single package build with
> cmake?
> 
> Any examples in the tree?

ifeq ($(BR2_PACKAGE_RPI_USERLAND),y)
LIBCEC_DEPENDENCIES += rpi-userland
LIBCEC_CONF_OPTS += \
        -DCMAKE_C_FLAGS="$(TARGET_CFLAGS) -lvcos -lvchiq_arm" \
        -DCMAKE_CXX_FLAGS="$(TARGET_CXXFLAGS) \
                -I$(STAGING_DIR)/usr/include/interface/vmcs_host/linux \
                -I$(STAGING_DIR)/usr/include/interface/vcos/pthreads"
endif

or

ifeq ($(BR2_ARM_CPU_ARMV7A)$(BR2_ARM_CPU_HAS_NEON),yy)
GNURADIO_CONF_OPTS += -DCMAKE_C_FLAGS="$(TARGET_CFLAGS) -march=armv7-a"
endif

Best regards,

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

  reply	other threads:[~2017-02-14 11:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13  9:35 [Buildroot] [PATCH] kmsxx: not available on m68k Peter Korsgaard
2017-02-13 12:29 ` Thomas Petazzoni
2017-02-13 14:32   ` Peter Korsgaard
2017-02-13 21:37     ` Waldemar Brodkorb
2017-02-14 10:15       ` Peter Korsgaard
2017-02-14 10:18         ` Thomas Petazzoni
2017-02-14 11:42         ` Waldemar Brodkorb
2017-02-14 11:58           ` Thomas Petazzoni [this message]
2017-02-14 12:10           ` 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=20170214125837.69821038@free-electrons.com \
    --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