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 v2] package/pkg-cmake.mk: add ccache support for host packages
Date: Sun, 21 Dec 2014 22:53:19 +0100	[thread overview]
Message-ID: <20141221225319.12501d7e@free-electrons.com> (raw)
In-Reply-To: <1418584321-10788-1-git-send-email-s.martin49@gmail.com>

Dear Samuel Martin,

On Sun, 14 Dec 2014 20:12:01 +0100, Samuel Martin wrote:
> This ccache support for host-cmake-package uses the same logic as the
> one done for the target packages in the toolchainfile.cmake file.
> 
> Signed-off-by: Samuel Martin <s.martin49@gmail.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

Seriously, do you test your patches before sending them?

> +# Set compiler variables.
> +ifeq ($(BR2_CCACHE),y)
> +CMAKE_HOST_C_COMPILER="$(HOST_DIR)/usr/bin/ccache"
> +CMAKE_HOST_CXX_COMPILER="$(HOST_DIR)/usr/bin/ccache"
> +CMAKE_HOST_C_COMPILER_ARG1="$(HOSTCC)"

This should have been HOSTCC_NOCCACHE.

> +CMAKE_HOST_CXX_COMPILER_ARG1="$(HOSTCXX)"

This should have been HOSTCXX_NOCCACHE.

Otherwise, HOSTCC and HOSTCXX already contains
"$(HOST_DIR)/usr/bin/ccache /usr/bin/gcc".


> +		-DCMAKE_C_COMPILER="$$(CMAKE_HOST_C_COMPILER) \

Missing closing double quote.

> +		-DCMAKE_C_COMCXX_COMPILER="$$(CMAKE_HOST_CXX_COMPILER) \

Really C_COMCXX_COMPILER ?

This was really a completely crappy and untested patch. How do you want
us to trust your future submissions if you submit such things?

I've applied after fixing this mess.

Thanks,

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

      reply	other threads:[~2014-12-21 21:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-14 19:12 [Buildroot] [PATCH v2] package/pkg-cmake.mk: add ccache support for host packages Samuel Martin
2014-12-21 21:53 ` 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=20141221225319.12501d7e@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