Re: [yocto] Custom eSDK build fails
I have made changes in populate_sdk_ext.bbclass to copy my layers during
do_populate_sdk and that works fine.
Now, I'm hitting failure at :
*ERROR: Failed to generate filtered task list for extensible SDK *( after
this it prints the contents of my custom conf-notes)
Looking at the source of this error, it comes from populate_sdk_ext.bbclass
-
https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/populate_sdk_ext.bbclass#n170
And its failing because its not finding a tasklist_bb_log.txt.
This text file contains logs of setscene tasks of all the packages built.
For some reason, this file is not getting auto-generated for my custom
image.
Any hints?
Warm Regards,
Priyanshu Sharma
On Wed, May 15, 2019 at 3:57 PM Priyanshu Sharma <
ms.priyanshu.sha...@gmail.com> wrote:
> I see that my custom layers are not being copied in
> /sdk-ext/image/opt/${DISTRO}/${POKY_VERSION}/layers. Though
> the conf files at
> /sdk-ext/image/opt/${DISTRO}/${POKY_VERSION}/conf.
>
> How can I include my layers also in this?
>
> Warm Regards,
> Priyanshu Sharma
>
> On Thu, May 2, 2019 at 3:12 PM Priyanshu Sharma <
> ms.priyanshu.sha...@gmail.com> wrote:
>
>> Hi,
>>
>> I've a custom Yocto layer and use that as TEMPLATECONF for building. My
>> custom layer also contains the image recipe based on pulsar-image (from
>> meta-ivi).
>>
>> I'm using Yocto 2.5. The extensible sdk build fails at
>> do_populate_sdk_ext task for my image recipe.
>>
>> $ bitbake -f -c populate_sdk_ext
>> Error -
>> Exception: FileNotFoundError: [Errno 2] No such file or directory:
>> '///sdk-ext/image//opt//2.5.1/conf/local.conf.bak'
>> ->
>> '///sdk-ext/image//opt//2.5.1/conf/local.conf'
>>
>> If I check the path, <>/sdk-ext/image//opt//2.5.1 , this
>> directory is getting created but getting deleted afterwards.
>> And the one left after build fails is -
>> <>/sdk-ext/image//opt//layers
>>
>> Is there any configuration to be modified/added for my custom image?
>>
>> Warm regards,
>> Priyanshu Sharma
>>
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] extensible SDK build failure
Hi Russell, I'm also hitting the same "unexpected" errors for my linux-yocto-xxx.bb recipe/tasks while building extensible SDK for my platform. How did it work for you? Warm Regards, Priyanshu Sharma -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom eSDK build fails
I see that my custom layers are not being copied in
/sdk-ext/image/opt/${DISTRO}/${POKY_VERSION}/layers. Though
the conf files at
/sdk-ext/image/opt/${DISTRO}/${POKY_VERSION}/conf.
How can I include my layers also in this?
Warm Regards,
Priyanshu Sharma
On Thu, May 2, 2019 at 3:12 PM Priyanshu Sharma <
ms.priyanshu.sha...@gmail.com> wrote:
> Hi,
>
> I've a custom Yocto layer and use that as TEMPLATECONF for building. My
> custom layer also contains the image recipe based on pulsar-image (from
> meta-ivi).
>
> I'm using Yocto 2.5. The extensible sdk build fails at do_populate_sdk_ext
> task for my image recipe.
>
> $ bitbake -f -c populate_sdk_ext
> Error -
> Exception: FileNotFoundError: [Errno 2] No such file or directory:
> '///sdk-ext/image//opt//2.5.1/conf/local.conf.bak'
> ->
> '///sdk-ext/image//opt//2.5.1/conf/local.conf'
>
> If I check the path, <>/sdk-ext/image//opt//2.5.1 , this directory
> is getting created but getting deleted afterwards.
> And the one left after build fails is -
> <>/sdk-ext/image//opt//layers
>
> Is there any configuration to be modified/added for my custom image?
>
> Warm regards,
> Priyanshu Sharma
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Custom eSDK build fails
Hi, I've a custom Yocto layer and use that as TEMPLATECONF for building. My custom layer also contains the image recipe based on pulsar-image (from meta-ivi). I'm using Yocto 2.5. The extensible sdk build fails at do_populate_sdk_ext task for my image recipe. $ bitbake -f -c populate_sdk_ext Error - Exception: FileNotFoundError: [Errno 2] No such file or directory: '///sdk-ext/image//opt//2.5.1/conf/local.conf.bak' -> '///sdk-ext/image//opt//2.5.1/conf/local.conf' If I check the path, <>/sdk-ext/image//opt//2.5.1 , this directory is getting created but getting deleted afterwards. And the one left after build fails is - <>/sdk-ext/image//opt//layers Is there any configuration to be modified/added for my custom image? Warm regards, Priyanshu Sharma -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to remove packages from Image coming because of RDEPENDS
Hi, How can we remove inclusion of any package which comes because some other package RDPENDS on it? For example, rpcbind recipe RDEPENDS on shadow and libpam packages, because of which if IMAGE_INSTALL+="rpcbind" is mentioned in recipe ( even though shadow and libpam are not added like this explicilty) , shadow and libpam packages get packaged in Image rootfs. This even includes any bin/sbin provided by shadow/libpam, even when they are not needed in rootfs. Is there an optimum way to control inclusion of RDEPENDS packages? One way is to use ROOTFS_POST_PROCESS and remove specific files after do_rootfs task is done. But is there a way to remove entire package, instead of removing each file ? Warm Regards, Priyanshu Sharma -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Yocto][meta-qt5][qtwayland]Qtwayland recipe fails with Yocto 2.5
The compilation of features.egl was failing because wayland-client.h was not found in Yocto 2.5 sysroot of QTbase. In yocto 2.2, the sysroot was common so qtbase was able to find this header even without dependencies. Adding DEPENDS=wayland in qtbase recipe is compiling qtbase and qtwayland successfully. The bitbake did not throw error for missing driver. It just printed it in logs. Warm Regards, Priyanshu Sharma On Mon, Apr 1, 2019 at 1:00 PM Priyanshu Sharma < ms.priyanshu.sha...@gmail.com> wrote: > The compilation of features.egl was failing because wayland-client.h was > not found in Yocto 2.5 sysroot of QTbase. In yocto 2.2, the sysroot was > common so qtbase was able to find this header even without dependencies. > Adding DEPENDS=wayland in qtbase recipe is compiling qtbase and qtwayland > successfully. > > The bitbake did not throw error for missing driver. It just printed it in > logs. > > Warm Regards, > Priyanshu Sharma > > On Wed, Mar 27, 2019 at 4:20 PM Priyanshu Sharma < > ms.priyanshu.sha...@gmail.com> wrote: > >> Found that the missing features.egl is provided by QTBase recipe. And in >> my case, qtbase is not compiling the feature "EGL" and thats why qtwayland >> fails to find it. >> >> egl is not included in PACKAGECONFIG of qtbase recipe. However, it used >> to be enabled with Yocto 2.2. >> Adding it PACKAGECONFIG[eg] of qtbase is not enabling it. How can egl be >> enabled in qtbase? >> >> Warm regards, >> Priyanshu Sharma >> >> On Tue, Mar 19, 2019 at 1:23 PM Priyanshu Sharma < >> ms.priyanshu.sha...@gmail.com> wrote: >> >>> Hi All, >>> >>> I'm consistently getting a build failure after upgrading Poky to 2.5 >>> from 2.2 on qtwayland >>> Yocto recipe from meta-qt5. >>> >>> The error looks like : >>> >>> | Running configuration tests... >>> | Checking for Wayland client library... yes >>> | Checking for Wayland cursor library... yes >>> | Checking for wayland-scanner... yes >>> | Checking for Wayland EGL library... yes >>> | Checking for wayland-server... yes >>> | Done running configuration tests. >>> | >>> | Configure summary: >>> | >>> | Qt Wayland Drivers: >>> | EGL no >>> | Raspberry Pi ... no >>> | XComposite EGL . no >>> | XComposite GLX . no >>> | DRM EGL no >>> | libhybris EGL .. no >>> | Qt Wayland Client yes >>> | Qt Wayland Compositor yes >>> | >>> | ERROR: Feature 'wayland-egl' was enabled, but the pre-condition >>> 'features.wayland-client && features.opengl && features.egl && >>> libs.wayland-egl' failed. >>> | >>> | ERROR: Feature 'wayland-egl' was enabled, but the pre-condition >>> 'features.wayland-server && features.opengl && features.egl && >>> libs.wayland-egl' failed. >>> | >>> | Check config.log for details. >>> | WARNING: exit code 1 from a shell command. >>> I've checked that only pre-condition "features.egl" is failing. >>> I've my own custom recipe which is providing virtual/egl and is set as >>> PREFERRED_PROVIDER also. >>> What is the missing dependency here when virtual/egl is provided? >>> What exactly is features.egl looking for? ( virtual/egl provides egl.pc ) >>> I've not changed anything in meta-qt5 layer. And the version is 5.9.2 QT5. >>> However, is fails with 5.12 also. >>> >>> >>> Warm Regards, >>> >>> Priyanshu Sharma >>> >>> >>> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Yocto][meta-qt5][qtwayland]Qtwayland recipe fails with Yocto 2.5
The compilation of features.egl was failing because wayland-client.h was not found in Yocto 2.5 sysroot of QTbase. In yocto 2.2, the sysroot was common so qtbase was able to find this header even without dependencies. Adding DEPENDS=wayland in qtbase recipe is compiling qtbase and qtwayland successfully. The bitbake did not throw error for missing driver. It just printed it in logs. Warm Regards, Priyanshu Sharma On Wed, Mar 27, 2019 at 4:20 PM Priyanshu Sharma < ms.priyanshu.sha...@gmail.com> wrote: > Found that the missing features.egl is provided by QTBase recipe. And in > my case, qtbase is not compiling the feature "EGL" and thats why qtwayland > fails to find it. > > egl is not included in PACKAGECONFIG of qtbase recipe. However, it used to > be enabled with Yocto 2.2. > Adding it PACKAGECONFIG[eg] of qtbase is not enabling it. How can egl be > enabled in qtbase? > > Warm regards, > Priyanshu Sharma > > On Tue, Mar 19, 2019 at 1:23 PM Priyanshu Sharma < > ms.priyanshu.sha...@gmail.com> wrote: > >> Hi All, >> >> I'm consistently getting a build failure after upgrading Poky to 2.5 from >> 2.2 on qtwayland >> Yocto recipe from meta-qt5. >> >> The error looks like : >> >> | Running configuration tests... >> | Checking for Wayland client library... yes >> | Checking for Wayland cursor library... yes >> | Checking for wayland-scanner... yes >> | Checking for Wayland EGL library... yes >> | Checking for wayland-server... yes >> | Done running configuration tests. >> | >> | Configure summary: >> | >> | Qt Wayland Drivers: >> | EGL no >> | Raspberry Pi ... no >> | XComposite EGL . no >> | XComposite GLX . no >> | DRM EGL no >> | libhybris EGL .. no >> | Qt Wayland Client yes >> | Qt Wayland Compositor yes >> | >> | ERROR: Feature 'wayland-egl' was enabled, but the pre-condition >> 'features.wayland-client && features.opengl && features.egl && >> libs.wayland-egl' failed. >> | >> | ERROR: Feature 'wayland-egl' was enabled, but the pre-condition >> 'features.wayland-server && features.opengl && features.egl && >> libs.wayland-egl' failed. >> | >> | Check config.log for details. >> | WARNING: exit code 1 from a shell command. >> I've checked that only pre-condition "features.egl" is failing. >> I've my own custom recipe which is providing virtual/egl and is set as >> PREFERRED_PROVIDER also. >> What is the missing dependency here when virtual/egl is provided? >> What exactly is features.egl looking for? ( virtual/egl provides egl.pc ) >> I've not changed anything in meta-qt5 layer. And the version is 5.9.2 QT5. >> However, is fails with 5.12 also. >> >> >> Warm Regards, >> >> Priyanshu Sharma >> >> >> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Yocto][meta-qt5][qtwayland]Qtwayland recipe fails with Yocto 2.5
Found that the missing features.egl is provided by QTBase recipe. And in my case, qtbase is not compiling the feature "EGL" and thats why qtwayland fails to find it. egl is not included in PACKAGECONFIG of qtbase recipe. However, it used to be enabled with Yocto 2.2. Adding it PACKAGECONFIG[eg] of qtbase is not enabling it. How can egl be enabled in qtbase? Warm regards, Priyanshu Sharma On Tue, Mar 19, 2019 at 1:23 PM Priyanshu Sharma < ms.priyanshu.sha...@gmail.com> wrote: > Hi All, > > I'm consistently getting a build failure after upgrading Poky to 2.5 from > 2.2 on qtwayland > Yocto recipe from meta-qt5. > > The error looks like : > > | Running configuration tests... > | Checking for Wayland client library... yes > | Checking for Wayland cursor library... yes > | Checking for wayland-scanner... yes > | Checking for Wayland EGL library... yes > | Checking for wayland-server... yes > | Done running configuration tests. > | > | Configure summary: > | > | Qt Wayland Drivers: > | EGL no > | Raspberry Pi ... no > | XComposite EGL . no > | XComposite GLX . no > | DRM EGL no > | libhybris EGL .. no > | Qt Wayland Client yes > | Qt Wayland Compositor yes > | > | ERROR: Feature 'wayland-egl' was enabled, but the pre-condition > 'features.wayland-client && features.opengl && features.egl && > libs.wayland-egl' failed. > | > | ERROR: Feature 'wayland-egl' was enabled, but the pre-condition > 'features.wayland-server && features.opengl && features.egl && > libs.wayland-egl' failed. > | > | Check config.log for details. > | WARNING: exit code 1 from a shell command. > I've checked that only pre-condition "features.egl" is failing. > I've my own custom recipe which is providing virtual/egl and is set as > PREFERRED_PROVIDER also. > What is the missing dependency here when virtual/egl is provided? > What exactly is features.egl looking for? ( virtual/egl provides egl.pc ) > I've not changed anything in meta-qt5 layer. And the version is 5.9.2 QT5. > However, is fails with 5.12 also. > > > Warm Regards, > > Priyanshu Sharma > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Yocto][meta-qt5][qtwayland]Qtwayland recipe fails with Yocto 2.5
Hi All, I'm consistently getting a build failure after upgrading Poky to 2.5 from 2.2 on qtwayland Yocto recipe from meta-qt5. The error looks like : | Running configuration tests... | Checking for Wayland client library... yes | Checking for Wayland cursor library... yes | Checking for wayland-scanner... yes | Checking for Wayland EGL library... yes | Checking for wayland-server... yes | Done running configuration tests. | | Configure summary: | | Qt Wayland Drivers: | EGL no | Raspberry Pi ... no | XComposite EGL . no | XComposite GLX . no | DRM EGL no | libhybris EGL .. no | Qt Wayland Client yes | Qt Wayland Compositor yes | | ERROR: Feature 'wayland-egl' was enabled, but the pre-condition 'features.wayland-client && features.opengl && features.egl && libs.wayland-egl' failed. | | ERROR: Feature 'wayland-egl' was enabled, but the pre-condition 'features.wayland-server && features.opengl && features.egl && libs.wayland-egl' failed. | | Check config.log for details. | WARNING: exit code 1 from a shell command. I've checked that only pre-condition "features.egl" is failing. I've my own custom recipe which is providing virtual/egl and is set as PREFERRED_PROVIDER also. What is the missing dependency here when virtual/egl is provided? What exactly is features.egl looking for? ( virtual/egl provides egl.pc ) I've not changed anything in meta-qt5 layer. And the version is 5.9.2 QT5. However, is fails with 5.12 also. Warm Regards, Priyanshu Sharma -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
