From: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
To: Moritz Blume <moritz.blume@bmw-carit.de>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3 2/2] cmake: Upgrade 2.8.12.2 -> 3.2.2
Date: Thu, 18 Jun 2015 14:30:01 +0200 [thread overview]
Message-ID: <5582B9C9.1060307@herbrechtsmeier.net> (raw)
In-Reply-To: <55818872.5000102@bmw-carit.de>
[-- Attachment #1: Type: text/plain, Size: 2090 bytes --]
Am 17.06.2015 um 16:47 schrieb Moritz Blume:
> On 11.06.2015 21:10, Stefan Herbrechtsmeier wrote:
>> Am 10.06.2015 um 09:36 schrieb Moritz Blume:
>>> Patches "qt4-fail-silent.patch" and "support-oe-qt4-tools-names.patch"
>>> were adapted in order to fit to CMake 3.2.2 (refer to the commit
>>> message in the respective patch for details).
>>> Patch "cmake-2.8.11.2-FindFreetype.patch" was dropped since it was
>>> rejected upstream and its functionality otherwise implemented in the
>>> meantime.
>>>
>>> Note that CMake 3 needs to have the full compiler path in the toolchain
>>> file (see cmake.bbclass).
>> Why is the full path needed?
>
> https://public.kitware.com/Bug/view.php?id=15251
>
> "Having a full path to the compiler is a new requirement starting in
> CMake 3.0. The incompatibility was introduced across a major version
> number bump and is considered acceptable. The project will have to be
> fixed to use a full path."
The documentions [1] says something else:
The CMAKE_<LANG>_COMPILER variables may be set to full paths, or to
names of compilers to search for in standard locations
> Without a full path, you get the following error message:
>
> CMake Error at CMakeLists.txt:5 (project):
> | The CMAKE_C_COMPILER:
> |
> | gcc
> |
> | is not a full path and was not found in the PATH.
> |
> | Tell CMake where to find the compiler by setting either the environment
> | variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full
> path to
> | the compiler, or to the compiler name if it is in the PATH.
>
But this messages also says that the compiler was not found in the PATH.
>>
>> Have you try to add STAGING_BINDIR_TOOLCHAIN to the
>> CMAKE_FIND_ROOT_PATH?
>
> I don't understand, is this related to the compiler path?
Yes, but this doesn't helps as CMAKE_<LAND>_COMPILER is not inside a
/bin path. CMake use find_program to get the full path in
Modules/CMakeDetermineCompiler.cmake.
<snip>
[1]
http://www.cmake.org/cmake/help/v3.2/manual/cmake-toolchains.7.html#cross-compiling-for-linux
[-- Attachment #2: Type: text/html, Size: 3834 bytes --]
prev parent reply other threads:[~2015-06-18 12:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 7:36 [PATCH v3 1/2] cmake: Whitespace fix Moritz Blume
2015-06-10 7:36 ` [PATCH v3 2/2] cmake: Upgrade 2.8.12.2 -> 3.2.2 Moritz Blume
2015-06-10 16:49 ` Burton, Ross
2015-06-10 19:41 ` Burton, Ross
2015-06-11 17:14 ` Stefan Herbrechtsmeier
2015-06-11 19:10 ` Stefan Herbrechtsmeier
2015-06-17 14:47 ` Moritz Blume
2015-06-18 12:30 ` Stefan Herbrechtsmeier [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=5582B9C9.1060307@herbrechtsmeier.net \
--to=stefan@herbrechtsmeier.net \
--cc=moritz.blume@bmw-carit.de \
--cc=openembedded-core@lists.openembedded.org \
/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.