Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Maxime Roussin-Bélanger" <maxime.roussinbelanger@gmail.com>
To: otavio.salvador@ossystems.com.br,
	openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/1] cmake: Use find_program if find_host_program is not available
Date: Tue, 27 Jun 2017 10:14:22 -0400	[thread overview]
Message-ID: <cover.1498512911.git.maxime.roussinbelanger@gmail.com> (raw)

When building an application with android toolchain there is no problem, but
using another toolchain that doesn't define the macro, cmake exit with en error.

The following changes since commit b8358bc61435ec996ecd6931fb6d6d41bb4f710b:

  bitbake: bitbake-selftest: add bb.tests.event to bitbake-selftest (2017-06-23 14:14:17 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib mroussin/fix_cmake_find_cuda_not_android
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mroussin/fix_cmake_find_cuda_not_android

Maxime Roussin-Bélanger (1):
  cmake: Use find_program if find_host_program is not available

 meta/recipes-devtools/cmake/cmake.inc              |  1 +
 ...e-find_program-if-find_host_program-is-no.patch | 36 ++++++++++++++++++++++
 2 files changed, 37 insertions(+)
 create mode 100644 meta/recipes-devtools/cmake/cmake/0001-FindCUDA-Use-find_program-if-find_host_program-is-no.patch

-- 
2.1.4



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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-27 14:14 Maxime Roussin-Bélanger [this message]
2017-06-27 14:14 ` [PATCH v2 1/1] cmake: Use find_program if find_host_program is not available Maxime Roussin-Bélanger
2017-06-27 14:32   ` Jussi Kukkonen
2017-06-27 14:31 ` ✗ patchtest: failure for cmake: Use find_program if find_host_program is not available (rev2) Patchwork

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=cover.1498512911.git.maxime.roussinbelanger@gmail.com \
    --to=maxime.roussinbelanger@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    /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