All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5] populate_sdk_ext fails
Date: Mon, 30 Jan 2017 23:13:17 +0100	[thread overview]
Message-ID: <20170130221317.GD13746@jama> (raw)
In-Reply-To: <F44878C7-F939-43ED-A849-F9392C7B604D@viavisolutions.com>

[-- Attachment #1: Type: text/plain, Size: 2467 bytes --]

On Mon, Jan 30, 2017 at 08:23:28PM +0000, Mike Nicholson wrote:
> Hello,
> 
> I sent the following the the openembedded-issues email list last month with no response.  I wanted to follow up with openembedded-devel in case ‘issues’ wasn’t the right mailing list.

This ML is correct one, openembedded-issues is quite dead with only 3
e-mails in last 5 years.

> I’m attempting to generate an extensible SDK that includes the meta-qt5 layer.  Generating a standard sdk via Yocto works just fine but generating the extensible sdk fails with the following error:
>  
> | NOTE: Executing create_sdk_files ...
> | DEBUG: Executing shell function create_sdk_files
> | touch: cannot touch '/home/nic47222/Projects/viavi-platform/viavi-bsp/build/tmp/work/mts-poky-linux-gnueabi/viavi-image-qt5/1.0-r0/sdk-ext/image//opt/poky/2.1.1/sysroots/x86_64-pokysdk-linux/usr/bin/qt5/qt.conf': No such file or directory
>  
> It appears that here https://github.com/meta-qt5/meta-qt5/blob/9aa870eecf6dc7a87678393bd55b97e21033ab48/classes/populate_sdk_qt5_base.bbclass#L7 the directory that should contain the qt.conf file does not exist.
>  
> Are there known issues with the populate_sdk_ext command and the meta-qt5 layer?
>  
> I can get generate the extensible SDK just fine if I make the following changes:

This looks OK to me, not sure why you're first one to report that (I'm
not using extensible SDKs), could you please send proper patch with this
(as described in README file)?

> diff --git a/classes/populate_sdk_qt5_base.bbclass b/classes/populate_sdk_qt5_base.bbclass
> index b6ce596..b66fe25 100644
> --- a/classes/populate_sdk_qt5_base.bbclass
> +++ b/classes/populate_sdk_qt5_base.bbclass
> @@ -4,6 +4,7 @@ inherit qmake5_paths
> create_sdk_files_prepend () {
>      # Generate a qt.conf file to be deployed with the SDK
>      qtconf=${SDK_OUTPUT}/${SDKPATHNATIVE}${OE_QMAKE_PATH_HOST_BINS}/qt.conf
> +    mkdir -p ${SDK_OUTPUT}/${SDKPATHNATIVE}${OE_QMAKE_PATH_HOST_BINS}
>      touch $qtconf
>      echo '[Paths]' >> $qtconf
>      echo 'Prefix = ${OE_QMAKE_PATH_PREFIX}' >> $qtconf
> --
> 2.7.4
>  
>  
> Thank you in advance for any help.
> 
> 
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

  reply	other threads:[~2017-01-30 22:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 20:23 [meta-qt5] populate_sdk_ext fails Mike Nicholson
2017-01-30 22:13 ` Martin Jansa [this message]
2017-01-31  4:14 ` Paul Eggleton

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=20170130221317.GD13746@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@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.