Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 01/11] pkg-cmake.mk: refactor the toolchainfile.cmake generation
Date: Sun, 01 Jun 2014 22:12:14 +0200	[thread overview]
Message-ID: <877g504cf5.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1401614673-3703-2-git-send-email-s.martin49@gmail.com> (Samuel Martin's message of "Sun, 1 Jun 2014 11:24:23 +0200")

>>>>> "Samuel" == Samuel Martin <s.martin49@gmail.com> writes:

 > This patch introduces a toolchainfile.cmake.in template which is filled
 > by Buildroot.

 > Using a toolchainfile.cmake.in template file allows to avoid overloading
 > quoting and/or escaping and it becomes much more similar to the
 > resulting file.

 > This patch also cleans up the quoting style.

 > Signed-off-by: Samuel Martin <s.martin49@gmail.com>
 > Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
 > Cc: Baruch Siach <baruch@tkos.co.il>

Committed with the stdin redirect changed as suggested by Thomas, thanks.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2014-06-01 20:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01  9:24 [Buildroot] [PATCH v4 00/11] CMake infrastructure refactoring Samuel Martin
2014-06-01  9:24 ` [Buildroot] [PATCH v4 01/11] pkg-cmake.mk: refactor the toolchainfile.cmake generation Samuel Martin
2014-06-01 10:54   ` Thomas Petazzoni
2014-06-01 20:12   ` Peter Korsgaard [this message]
2014-06-01  9:24 ` [Buildroot] [PATCH v4 02/11] pkg-cmake.mk: do not hardcode absolute path in toolchainfile.cmake Samuel Martin
2014-06-01 10:57   ` Thomas Petazzoni
2014-06-01 20:16   ` Peter Korsgaard
2014-06-01  9:24 ` [Buildroot] [PATCH v4 03/11] pkg-cmake.mk: enable ccache for cmake packages Samuel Martin
2014-06-01 10:57   ` Thomas Petazzoni
2014-06-01 20:17   ` Peter Korsgaard
2014-06-01  9:24 ` [Buildroot] [PATCH v4 04/11] rpi-userland: cleanup *_CONF_OPT Samuel Martin
2014-06-01 11:04   ` Thomas Petazzoni
2014-06-01  9:24 ` [Buildroot] [PATCH v4 05/11] xbmc: fix missing libraries from rpi-userland Samuel Martin
2014-06-01  9:24 ` [Buildroot] [PATCH v4 06/11] pkg-cmake.mk: globally disable BUILD_TESTING flag Samuel Martin
2014-06-01 11:05   ` Thomas Petazzoni
2014-06-01 20:18   ` Peter Korsgaard
2014-06-01  9:24 ` [Buildroot] [PATCH v4 07/11] pkg-cmake.mk: globally drive the CMAKE_BUILD_TYPE flag using BR2_ENABLE_DEBUG Samuel Martin
2014-06-01 11:06   ` Thomas Petazzoni
2014-06-01 20:18   ` Peter Korsgaard
2014-06-01  9:24 ` [Buildroot] [PATCH v4 08/11] openpowerlink: do not override CMAKE_BUILD_TYPE Samuel Martin
2014-06-01 11:07   ` Thomas Petazzoni
2014-06-01 20:19   ` Peter Korsgaard
2014-06-01  9:24 ` [Buildroot] [PATCH v4 09/11] opencv: " Samuel Martin
2014-06-01 11:07   ` Thomas Petazzoni
2014-06-01 20:20   ` Peter Korsgaard
2014-06-01  9:24 ` [Buildroot] [PATCH v4 10/11] flann: " Samuel Martin
2014-06-01 11:07   ` Thomas Petazzoni
2014-06-01 20:20   ` Peter Korsgaard
2014-06-01  9:24 ` [Buildroot] [PATCH v4 11/11] qhull: " Samuel Martin
2014-06-01 11:07   ` Thomas Petazzoni
2014-06-01 20:20   ` Peter Korsgaard
2014-06-01 11:08 ` [Buildroot] [PATCH v4 00/11] CMake infrastructure refactoring Thomas Petazzoni
2014-06-01 20:20   ` 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=877g504cf5.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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