All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: "Chinthamol CS." <Chinthamol.CS@nestgroup.net>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: QT5.8 -qtwebengine SDK generation fails
Date: Tue, 8 May 2018 10:27:27 -0700	[thread overview]
Message-ID: <CAMKF1srYbXcRm_Zb=u2tqUW272VEjAGytOVsUCUSfbLqOARooQ@mail.gmail.com> (raw)
In-Reply-To: <5304B3CDBC3FA44CAED287F54088A0CA236C39CD@MBCHN01.chn.nestgroup.net>

there isnt enough information in the logs that can be built upon to
help you. you might want to enable some verbosity with smart and try
to find out why it fails.

secondly, try the same with newer releases and see if the problem is
reproducible.

On Sun, May 6, 2018 at 11:18 PM, Chinthamol CS.
<Chinthamol.CS@nestgroup.net> wrote:
> Hi,
>
> We are using a i.MX8 board and we need to develop QT application based on
> qtwebengine. QT version used here is 5.8.
>
> We are using QT Creator with an external tool chain. we have to populate the
> SDK out of our yocto image.
>
> When we start to include qtwebengine to the
> packagegroup-qt5-toolchain-target.bb, we are getting errors. This step is
> required as otherwise the qtwebengine binary will be missing in the SDK and
> QT Creator will complain about that.
>
> We are using the imx-morty branch with Kernel Version  as 4.9.51of the i.MX
> yocto BSP.
>
> The problem can be triggered with either "bitbake -c populate_sdk
> image-name" or with "bitbake meta-toolchain-qt5".
>
> Error log is attached with this email. We really cannot find the reason why.
>
> Any tips for how to proceed?
>
> Below mentioned link says, Use webkit instead of webengine.
>
> https://community.nxp.com/thread/473203#
>
> Anyway we have to use qtwebengine for web browsing, not qtwebkit.. Please
> provide one solution to resolve this issue.
>
> Any help from anyone is greatly appreciated.
>
>
>
> Thanks,
>
> Chintha
>
>
>
>
>
> ________________________________
>
> Confidentiality Statement / Disclaimer : This message and any attachments is
> intended for the sole use of the intended recipient. It may contain
> confidential information. Any unauthorized use, dissemination or
> modification is strictly prohibited. If you are not the intended recipient,
> please notify the sender immediately then delete it from all your systems,
> and do not copy, use or print. Internet communications are not secure and it
> is the responsibility of the recipient to make sure that it is
> virus/malicious code exempt.
>
> The company/sender cannot be responsible for any unauthorized alterations or
> modifications made to the contents. If you require any form of confirmation
> of the contents, please contact the company/sender. The company/sender is
> not liable for any errors or omissions in the content of this message.
>
> ________________________________
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>


  parent reply	other threads:[~2018-05-08 17:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07  6:18 QT5.8 -qtwebengine SDK generation fails Chinthamol CS.
2018-05-08 10:26 ` Zoran Stojsavljevic
2018-05-08 17:27 ` Khem Raj [this message]
2018-05-07  8:36 Nishina A. Pervin

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='CAMKF1srYbXcRm_Zb=u2tqUW272VEjAGytOVsUCUSfbLqOARooQ@mail.gmail.com' \
    --to=raj.khem@gmail.com \
    --cc=Chinthamol.CS@nestgroup.net \
    --cc=yocto@yoctoproject.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.