From: Pascal Bach <pascal.bach@siemens.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v4 0/4] cmake.bbclass improvements
Date: Fri, 19 Oct 2018 13:58:54 +0200 [thread overview]
Message-ID: <953e09ed-9f74-a048-e8e7-c26b19be3eb2@siemens.com> (raw)
In-Reply-To: <CAMKF1somO_+n1w=ek=vcv1p=RuX-3m1tiho+qi7P_z4xocgefQ@mail.gmail.com>
On 18.10.2018 17:28, Khem Raj wrote:
> On Thu, Oct 18, 2018 at 7:58 AM Pascal Bach <pascal.bach@siemens.com> wrote:
>>
>> On 17.10.2018 20:50, Khem Raj wrote:
>>> On Wed, Oct 17, 2018 at 3:43 AM Pascal Bach <pascal.bach@siemens.com> wrote:
>>>> This patchset is unmodified from v3. It is just rebased on top of master which
>>>> already includes a fixed version of libproxy and piglit.
>>>>
>>>> I built all cmake based recipes in oe-core (qemuarm64) and did not find any more issues.
>>>>
>>> Can you run world builds on meta-openembedded repositories with
>>> this series applied and also compile some other large projects which
>>> use cmake like meta-browser
>> I can try but usually I get into trouble with the proxy because there are always some recipes that fetch from some location via some protocol that doesn't work.
> Once the current cycle of builds is done on OE
> builders I will try to schedule this in OE builds and
> see where it ends up. hopefully by this weekend.
I was able to do a world build with all layers of meta-oe and there are a few failures:
Two of wich I think are related to cmake:
- libyui-ncurses => messing around with hardcoded path in their cmake setup
- civetweb => still trying to figure out what exactly goes wrong
The following I was unable to build due to fetch problems:
- oscam
I will try to send patches for these two recipes.
>>>> Pascal Bach (4):
>>>> cmake.bbclass: use CMAKE_SYSTEM_LIBRARY_PATH instead of
>>>> CMAKE_LIBRARY_PATH
>>>> cmake.bbclass: search both sysroot-native and host for native packages
>>>> cmake.bbclass: move CMAKE_NO_SYSTEM_FROM_IMPORTED to toolchain.cmake
>>>> cmake.bbclass: allow cmake to find hosttools
>>>>
>>>> meta/classes/cmake.bbclass | 24 +++++++++++++++---------
>>>> 1 file changed, 15 insertions(+), 9 deletions(-)
>>>>
>>>> --
>>>> 2.11.0
>>>>
>>>> --
>>>> _______________________________________________
>>>> Openembedded-core mailing list
>>>> Openembedded-core@lists.openembedded.org
>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2018-10-19 11:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 10:42 [PATCH v4 0/4] cmake.bbclass improvements Pascal Bach
2018-10-17 10:42 ` [PATCH v4 1/4] cmake.bbclass: use CMAKE_SYSTEM_LIBRARY_PATH instead of CMAKE_LIBRARY_PATH Pascal Bach
2018-10-17 10:42 ` [PATCH v4 2/4] cmake.bbclass: search both sysroot-native and host for native packages Pascal Bach
2018-10-17 16:24 ` Burton, Ross
2018-10-18 15:05 ` Pascal Bach
2018-10-18 19:44 ` Burton, Ross
2018-10-17 10:42 ` [PATCH v4 3/4] cmake.bbclass: move CMAKE_NO_SYSTEM_FROM_IMPORTED to toolchain.cmake Pascal Bach
2018-10-17 10:42 ` [PATCH v4 4/4] cmake.bbclass: allow cmake to find hosttools Pascal Bach
2018-10-17 18:50 ` [PATCH v4 0/4] cmake.bbclass improvements Khem Raj
2018-10-18 14:58 ` Pascal Bach
2018-10-18 15:28 ` Khem Raj
2018-10-19 11:58 ` Pascal Bach [this message]
2024-12-13 20:46 ` Manuel Leonhardt
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=953e09ed-9f74-a048-e8e7-c26b19be3eb2@siemens.com \
--to=pascal.bach@siemens.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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