yocto@lists.yoctoproject.org

How to write custom recipe to install AWS C SDK from github #dunfell #linux #yocto

Vijay Rakesh Munganda

#51612

Hi,

I'm trying to write a recipe to install AWS SDK into the build(https://github.com/aws/aws-iot-device-sdk-embedded-C), but I complete don't know how to do it. Based on online example https://github.com/joaocfernandes/Learn-Yocto/blob/master/develop/Recipe-CMake.md I have written my recipe file and download the sdk into files folder of my recipe. When I run build do_configure got failed.

SUMMARY = "AWS IoT SDK EMBEDDED C"

SECTION = "examples"

LICENSE = "MIT"

LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

SRC_URI = "file://CMakeLists.txt"

S = "${WORKDIR}"

inherit cmake

EXTRA_OECMAKE = ""

I know it is wrong, but kindly please someone help to write it correctly, thank you.

Thanks & Regards,
VR

Re: #yocto #yocto

Nicolas Jeker

#51611

Hi Steve

On Tue, 2020-12-01 at 20:06 +0000, Monsees, Steven C (US) via
lists.yoctoproject.org wrote:
 
I still haven’t been able to track this down, can someone tell me in
what package is the banner output generated ? I'm not sure to what lines you refer by "banner", so I just wrote my
thoughts to both below.

Both are probably produced by getty, either util-linux-agetty or
systemd-getty.

Thanks,
Steve
From: yocto@... [mailto: 
yocto@...]On Behalf Of Monsees, Steven C (US) via
lists.yoctoproject.org
Sent: Wednesday, November 18, 2020 8:08 AM
To: yocto@...
Subject: [yocto] #yocto
 
                             ***WARNING***
EXTERNAL EMAIL -- This message originates from outside our
organization.
 
  
I was going through the kernel boot output and saw the following
output, can someone tell me why this might be popping up and how I
might modify configuration to resolve? :
. 
. 
LIMWS (BAE LIMWS base distro) 3.0.4 sbcb-default ttyS0   This "banner" output is the content of /etc/issue (which gets installed
by the base-file package).

-sh: cannot set terminal process group (1137): Inappropriate ioctl
for device
-sh: no job control in this shell 
. The error you see about the shell is probably getty failing to open a
shell.

Maybe this could be relevant:
https://unix.stackexchange.com/questions/338214/error-trying-to-run-agetty-in-a-runit-based-linux-installation

. 
  
Thanks, 
Steve

qt5 directory not creating using qt5.15.0 master branch

sateesh m

#51610

Hi Guys,

I am trying to build qt support image to my yocto .I am using meta-qt5 master sources,after build its not creating qt5 directory path in the /usr/lib path as well as /usr/share/path but . but when i build x86 its created
x86 i got :
$ /usr/share/qt5$ ls
$usr/lib/qt5/bin$ ls

can you please help me if anyone knows this issue.

thanks in advance.

Regards,
Sateesh

Re: Raspberry PI enabling MMC1

chuck kamas

#51609

Thank you all. That is good information to know! However, I already had a custom machine config that I was able to drop the overlay into. Once I had the correct overlay enabling the sdio, the SD card works!

Thanks again for all of your help.

Show quoted text

On 11/20/20 4:22 AM, Erik Boto wrote:

On Thu, Nov 19, 2020 at 7:21 PM chuck kamas via lists.yoctoproject.org
<chuckkamas=yahoo.com@...> wrote:

Making some progress here!


I added a compiled version of the attached device tree and now the mmc1 shows up in my yocto image! Yes! Now I need to find out the secret magic in that tree that I need to add...

If I'm not mistaken that should be done by appending
RPI_KERNEL_DEVICETREE_OVERLAYS. If you don't have your own custom
machine configuration where this could be added, try adding the
following to local.conf:

RPI_KERNEL_DEVICETREE_OVERLAYS_append = " overlays/sdio.dtbo "

Cheers,
Erik


Chuck


On 11/18/20 7:59 PM, chuck kamas via lists.yoctoproject.org wrote:

Raj,


I found out how to debug the boot process of the PI from:

https://github.com/raspberrypi/documentation/blob/master/hardware/raspberrypi/bootmodes/README.md

by turning on the boot code debug.

sed -i -e "s/BOOT_UART=0/BOOT_UART=1/" bootcode.bin


I found out that the sdio overlay does not exist!

MESS:00:00:07.868162:0: dtdebug: Failed to open overlay file 'overlays/sdio.dtbo'
MESS:00:00:07.874093:0: Failed to load overlay 'sdio'
MESS:00:00:07.878881:0: brfs: File read: /mfs/sd/overlays/sdio.dtbo
MESS:00:00:07.891322:0: brfs: File read: /mfs/sd/cmdline.txt


So what am I missing on how to turn on the sdio on GPIO22-27? Is it not an overlay and instead a driver/other code/linux config that needs to be set?


Chuck


On 11/17/20 4:29 PM, chuck kamas via lists.yoctoproject.org wrote:

Raj,


Thanks for taking the time to respond. I thought of that too. My custom Yocto build has the line to turn on the sdio in it:

dtoverlay=sdio,poll_once=off


I have attached the entire file: config.txt.yocto

However, the Rasbian image does not have any mention of the dtoverlay for the sdio.  Curious. See config.txt attached.


Thanks for the help!

Chuck


On 11/17/20 12:08 AM, Khem Raj wrote:

On Mon, Nov 16, 2020 at 11:43 PM chuck kamas via
lists.yoctoproject.org <chuckkamas=yahoo.com@...>
wrote:

Hi all,


I have been spinning my wheels for two days trying to discover how to
enable MMC1 on a CM3. This is the one on GPIO22-27. I can boot Rasbian
on the CM3 and it inits the MMC1 and its pins just fine. I can
read/write to my SD card from it etc. However, when I build yocto it
leaves the GPIOS22-27 in gpio mode and does not set them to MMC1 mode.
I have tried changing the device tree as described here:

https://stackoverflow.com/questions/44702426/how-to-setup-an-own-device-tree-for-a-raspberrypi-in-yocto

That compiles and add the .dtbo to my build, but still the GPIOS are not
set to MMC1 mode.

cat /sys/kernel/debug/pinctrl/*gpio*/pinmux-pins
Pinmux settings per pin
Format: pin (name): mux_owner gpio_owner hog?
....

pin 22 (gpio22): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 23 (gpio23): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 24 (gpio24): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 25 (gpio25): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 26 (gpio26): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 27 (gpio27): (MUX UNCLAIMED) (GPIO UNCLAIMED)

.....

I have looked at:

https://ralimtek.com/raspberry%20pi/electronics/software/raspberry_pi_secondary_sd_card/


Any ideas of where to look next to turn on the sdio would be appreciated!


what does /boot/config.txt look like on raspbian and yocto built images

Chuck

Re: #yocto #yocto

Monsees, Steven C (US)

#51608

I still haven’t been able to track this down, can someone tell me in what package is the banner output generated ?

Thanks,

Steve

Show quoted text

From: yocto@... [mailto:yocto@...] On Behalf Of Monsees, Steven C (US) via lists.yoctoproject.org
Sent: Wednesday, November 18, 2020 8:08 AM
To: yocto@...
Subject: [yocto] #yocto

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.

I was going through the kernel boot output and saw the following output, can someone tell me why this might be popping up and how I might modify configuration to resolve? :

.

LIMWS (BAE LIMWS base distro) 3.0.4 sbcb-default ttyS0

-sh: cannot set terminal process group (1137): Inappropriate ioctl for device

-sh: no job control in this shell

.

Thanks,

Steve

Adding modules to Apache2 during build

mailings@...

#51607

Hello all:

Thank you to all who post to help on the list. I have been helped so many times by just doing a search here.

I do have a question that I have been unable to solve on my own...

I have Apache2 and PHP installed and functional. I have also included "PAM" using:

PACKAGECONFIG_pn-php = " sqlite3 imap opcache openssl ${@bb.utils.filter('DISTRO_FEATURES', 'ipv6 pam', d)} apache2"

However, I need to add "libapache2-mod-authnz-external", "pwauth", and "libapache2-mod-authz-unixgroup" to my build. I've tried adding these to my local.conf in the line above and even tried it in my IMAGE_INSTALL_append section. When I add it to PACKAGECONFIG_pn-php I get a "do_configure: QA Issue" that it is an invalid packageconfig. If I put it in IMAGE_INSTALL_appeng I get an error that nothing provides the packages.

I know I'm missing something or not thinking of this correctly. Maybe it's not that I need to add a new package, but a module feature to Apache2? If someone could point me to where I can find an answer, I would appreciate it.

Thanks much.

-Joe

Re: [docs] Yocto Project Technical Documentation Request For Quote

Nicolas Dechesne

#51606

On Tue, Dec 1, 2020 at 7:32 PM akuster808 <akuster808@...> wrote:

On 11/30/20 11:42 PM, Nicolas Dechesne wrote:
> hi there,
>
> The Yocto Project is looking to hire a technical writer to develop and
> maintain the many documents the project supplies the greater
> community, including the official Yocto Project documentation website [1].
>
> We expect to build a long term relationship with this technical
> documentation person, and estimate that the workload for this role
> should be no more than 50%, spread evenly throughout the year.

Should this be posted on the YP Jobs page?

Good idea. I've done it now!

-armin
>
> For more information, please check [2].
>
> cheers
> nico
>
> [1] https://docs.yoctoproject.org/
> [2] https://www.yoctoproject.org/yocto-project-technical-documentation-request-for-quote/
>
>
>

Re: [docs] Yocto Project Technical Documentation Request For Quote

Armin Kuster

#51605

On 11/30/20 11:42 PM, Nicolas Dechesne wrote:
hi there,

The Yocto Project is looking to hire a technical writer to develop and
maintain the many documents the project supplies the greater
community, including the official Yocto Project documentation website [1].

We expect to build a long term relationship with this technical
documentation person, and estimate that the workload for this role
should be no more than 50%, spread evenly throughout the year.Should this be posted on the YP Jobs page?
-armin

For more information, please check [2].

cheers
nico

[1] https://docs.yoctoproject.org/
[2] https://www.yoctoproject.org/yocto-project-technical-documentation-request-for-quote/

Yocto Project Status WW48'20

Stephen Jolley

#51604

Current Dev Position: YP 3.3 M1 development

Next Deadline: 7th December 2020 YP 3.3 M1 build

Next Team Meetings:

Bug Triage meeting Thursday Dec. 3rd at 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
Monthly Project Meeting Tuesday Dec. 1st at 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09 )
Weekly Engineering Sync Tuesday Dec. 8th at 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09 )
Twitch - See https://www.twitch.tv/theyoctojester

Key Status/Updates:

YP 3.1.4 has been through QA and is now under review for release.
YP 3.3 M1 is due to be built next week
YP 3.3 development in master is continuing as patches are reviewed, tested and merged.
A number of python3 modules have moved to OE-Core, specifically around allowing pytest to operate there as a number of other recipes depend upon it and this seemed the most logical solution.
Various improvements have been made to the buildbot UI on the autobuilder and these have now been deployed on our live instance. The helper changes to improve the log separation and make the differences between builds clearer has also merged for master.
Intermittent autobuilder issues continue to occur. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

Ways to contribute:

There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
There are bugs that are currently unassigned for YP 3.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.3_Unassigned_Enhancements.2FBugs
We’d welcome new maintainers for recipes in OE-Core. Please see the list at: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to “Unassigned” soon to help facilitate this.

YP 3.3 Milestone Dates:

YP 3.3 M1 build date 2020/12/07
YP 3.3 M1 Release date 2020/12/18
YP 3.3 M2 build date 2021/01/18
YP 3.3 M2 Release date 2021/01/29
YP 3.3 M3 build date 2021/03/01
YP 3.3 M3 Release date 2021/03/12
YP 3.3 M4 build date 2021/04/05
YP 3.3 M4 Release date 2021/04/30

Planned upcoming dot releases:

YP 3.1.4 is just out of QA
YP 3.2.1 build date 2020/11/16
YP 3.2.1 release date 2020/12/4
YP 3.1.5 build date 2021/01/11
YP 3.1.5 release date 2021/01/22
YP 3.2.2 build date 2021/02/08
YP 3.2.2 release date 2021/02/19
YP 3.1.6 build date 2021/02/22
YP 3.1.6 release date 2021/03/05
YP 3.1.7 build date 2021/03/22
YP 3.1.7 release date 2021/04/02

Tracking Metrics:

WDD 2527 (last week 2532) (https://wiki.yoctoproject.org/charts/combo.html)
Poky Patch Metrics

Total patches found: 1283 (last week 1279)
Patches in the Pending State: 496 (39%) [last week 497 (39%)]

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status

[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

( Cell: (208) 244-4460

* Email: sjolley.yp.pm@...

Re: QA notification for completed autobuilder build (yocto-3.1.4.rc1)

Sangeeta Jain

#51603

Hello all,

This is the full report for yocto-3.1.4.rc1:  
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults

======= Summary ========
No high milestone defects. 

new issue found 

BUG id:14138 - [QA 3.1.4 RC1] failure in oe-core manual test: test_bitbake_devshell
   
Bugs verified:

BUG id:14071 - [QA 3.1.3 RC1] failure in ptest : perl.t/re/pat 
   Verified Fixed.

Existing bugs observed in this release:

BUG id:14055 - [QA 3.2 M3 RC1] failure in oe-core manual test: test_dependency_explorer_is_launched
  
======= Bugs ========
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14138
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14071
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14055

Thanks,
Sangeeta

Show quoted text

-----Original Message-----
From: Pokybuild User <pokybuild@...>
Sent: Thursday, 26 November, 2020 12:14 PM
To: yocto@...
Cc: otavio@...; yi.zhao@...; Sangal, Apoorv
<apoorv.sangal@...>; Yeoh, Ee Peng <ee.peng.yeoh@...>; Chan,
Aaron Chun Yew <aaron.chun.yew.chan@...>;
richard.purdie@...; akuster808@...;
sjolley.yp.pm@...; Jain, Sangeeta <sangeeta.jain@...>;
steve@...
Subject: QA notification for completed autobuilder build (yocto-3.1.4.rc1)


A build flagged for QA (yocto-3.1.4.rc1) was completed on the autobuilder and is
available at:


    https://autobuilder.yocto.io/pub/releases/yocto-3.1.4.rc1


Build hash information:

bitbake: 89fc9450abefd682266efcbfa031d1ef115ff1a7
meta-arm: e18ee052f75da60655fb434ff24a463a8fb36781
meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
meta-intel: 541c7256c1b6acba35d1116a1483b6594d189e3a
meta-kernel: f9d30c65d08c9cef20d6487a7aff0fff40acc823
meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7
oecore: b885888df67eb5cdb3b82f4f0a07369a449e223b
poky: 424296bf9bb4bae27febf91bce0118df09ce5fa1



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@...

hostapd_free_hapd_data: Interface wlan0 wasn't started #linux #kernel #dunfell

Vijay Rakesh Munganda

#51602

Hi,

I'm new to Yocto Project/Embedded Linux. I had added hostapd recipe (https://layers.openembedded.org/layerindex/recipe/28409/) into my build image, and when I try to run "hostapd hostapd.conf" in terminal, I get the below error.

Configuration file: hostapd.conf

nl80211: Could not configure driver mode

nl80211: deinit ifname=wlan0 disabled_11b_rates=0

nl80211 driver initialization failed.

wlan0: interface state UNINITIALIZED->DISABLED

wlan0: AP-DISABLED

wlan0: CTRL-EVENT-TERMINATING

hostapd_free_hapd_data: Interface wlan0 wasn't started

I had also killed wpa_supplicant, but still I get same error. Kindly please help me with this issue.

Thanks & Regards,
VR.

Yocto Project Technical Documentation Request For Quote

Nicolas Dechesne

#51601

hi there,

The Yocto Project is looking to hire a technical writer to develop and maintain the many documents the project supplies the greater community, including the official Yocto Project documentation website [1].

We expect to build a long term relationship with this technical documentation person, and estimate that the workload for this role should be no more than 50%, spread evenly throughout the year.

For more information, please check [2].

cheers

nico

[1] https://docs.yoctoproject.org/

[2] https://www.yoctoproject.org/yocto-project-technical-documentation-request-for-quote/

Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am on the first Tuesday (PDT)

Stephen Jolley

#51600

All,

Just a reminder we will hold the monthly Yocto Project Technical Meeting at 8am PST tomorrow. (12/1)

Yocto Project Technical Team Meeting: We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional):

Yocto IRC: http://webchat.freenode.net/?channels=#yocto

Wiki: https://www.yoctoproject.org/public-virtual-meetings/

When Monthly from 8am to 9am on the first Tuesday Pacific Time

Where Zoom Meeting: https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09

We are tracking the minutes at: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit?pli=1 Please request access if you want to assist in editing them. The world should have view access.

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

( Cell: (208) 244-4460

* Email: sjolley.yp.pm@...

M+ & H bugs with Milestone Movements WW48

Stephen Jolley

#51599

All,

YP M+ or high bugs which moved to a new milestone in WW48 are listed below:

Priority	Bug ID	Short Description	Changer	Owner	Was	Became
Medium+	12760	CMake Toolchain File Has Wrong Module Path	richard.purdie@...	unassigned@...	3.2 M4	3.3 M2

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

( Cell: (208) 244-4460

* Email: sjolley.yp.pm@...

Enhancements/Bugs closed WW48!

Stephen Jolley

#51598

All,

The below were the owners of enhancements or bugs closed during the last week!

Who	Count
richard.purdie@...	4
stacy.gaikovaia@...	1
fede@...	1
bruce.ashfield@...	1
Grand Total	7

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

( Cell: (208) 244-4460

* Email: sjolley.yp.pm@...

Current high bug count owners for Yocto Project 3.3

Stephen Jolley

#51597

All,

Below is the list as of top 47 bug owners as of the end of WW48 of who have open medium or higher bugs and enhancements against YP 3.3. There are 103 possible work days left until the final release candidates for YP 3.3 needs to be released.

Who	Count
richard.purdie@...	37
ross@...	24
david.reyna@...	21
bruce.ashfield@...	19
bluelightning@...	18
JPEWhacker@...	12
timothy.t.orling@...	12
sakib.sajal@...	11
mark.morton@...	11
trevor.gamblin@...	9
kai.kang@...	9
akuster808@...	9
Qi.Chen@...	6
raj.khem@...	5
yi.zhao@...	4
stacy.gaikovaia@...	4
mingli.yu@...	4
idadelm@...	4
randy.macleod@...	4
chee.yang.lee@...	3
alejandro@...	3
mostthingsweb@...	3
hongxu.jia@...	3
jaewon@...	2
jon.mason@...	2
matthewzmd@...	2
ydirson@...	2
saul.wold@...	2
pokylinux@...	2
jeanmarie.lemetayer@...	2
nicolas.dechesne@...	2
kergoth@...	1
joe.slater@...	1
anuj.mittal@...	1
shachar@...	1
mark.hatle@...	1
akuster@...	1
aehs29@...	1
dl9pf@...	1
Martin.Jansa@...	1
kexin.hao@...	1
apoorvsangal@...	1
liezhi.yang@...	1
mhalstead@...	1
maxime.roussinbelanger@...	1
matt.ranostay@...	1
kamensky@...	1
Grand Total	267

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

( Cell: (208) 244-4460

* Email: sjolley.yp.pm@...

Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley

#51596

All,

The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project. If anyone can help, please take ownership of the bug and send patches! If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.

Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 330 unassigned or newcomer bugs.

We're hoping people may be able to spare some time now and again to help out with these. Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system. There are also roughly four different "priority" classes right now, “3.2”, “3.3, "3.99" and "Future", the more pressing/urgent issues being in "3.2" and then “3.3”.

Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account). The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

( Cell: (208) 244-4460

* Email: sjolley.yp.pm@...

Yoctoproject ad Qt Commercial License.

Mauro Ziliani

#51595

Hi all.

Anyone has experience with Qt Commercial and Yocto Project?

Best regards,

Mauro Ziliani

Re: [meta-raspberrypi][PATCH] userland: add knob for ALL_APPS

Andrei Gherzan

#51594

Hi,

On Fri, Nov 27, 2020 at 10:16 AM Trevor Woerner <twoerner@...> wrote:

The userland sources include a bunch of sample applications. Add an "allapps"
PACKAGECONFIG to allow the user to build the additional optional applications.

Signed-off-by: Trevor Woerner <twoerner@...>

Merged to master. Thanks, Trevor.

---

Andrei

Include a clpru compiler in the SDK

Alessio Igor Bogani <alessioigorbogani@...>

#51593

Hi all,

I would like produce an SDK for the my image which includes the clpru
compiler  (a closed-source compiler made available by meta-ti) for the
PRUSS (an MCU embedded in the TI Sitara CPUs) so I have added in my
image's recipe:
TOOLCHAIN_HOST_TASK_append += "nativesdk-ti-cgt-pru"
Unfortunately it doesn't work:
[...]
Error:
Problem: conflicting requests
- nothing provides libpthread.so.0 needed by
nativesdk-ti-cgt-pru-2.3.2-r0.x86_64_nativesdk
- nothing provides libdl.so.2 needed by
nativesdk-ti-cgt-pru-2.3.2-r0.x86_64_nativesdk
- nothing provides libm.so.6 needed by
nativesdk-ti-cgt-pru-2.3.2-r0.x86_64_nativesdk
- nothing provides libc.so.6(GLIBC_2.3) needed by
nativesdk-ti-cgt-pru-2.3.2-r0.x86_64_nativesdk
- nothing provides libdl.so.2(GLIBC_2.0) needed by
nativesdk-ti-cgt-pru-2.3.2-r0.x86_64_nativesdk
- nothing provides libdl.so.2(GLIBC_2.1) needed by
nativesdk-ti-cgt-pru-2.3.2-r0.x86_64_nativesdk
- nothing provides libm.so.6(GLIBC_2.0) needed by
nativesdk-ti-cgt-pru-2.3.2-r0.x86_64_nativesdk
- nothing provides libpthread.so.0(GLIBC_2.0) needed by
nativesdk-ti-cgt-pru-2.3.2-r0.x86_64_nativesdk
- nothing provides libpthread.so.0(GLIBC_2.1) needed by
nativesdk-ti-cgt-pru-2.3.2-r0.x86_64_nativesdk
- nothing provides libpthread.so.0(GLIBC_2.2) needed by
nativesdk-ti-cgt-pru-2.3.2-r0.x86_64_nativesdk
- nothing provides libpthread.so.0(GLIBC_2.2.3) needed by
nativesdk-ti-cgt-pru-2.3.2-r0.x86_64_nativesdk
- nothing provides libpthread.so.0(GLIBC_2.3.2) needed by
nativesdk-ti-cgt-pru-2.3.2-r0.x86_64_nativesdk
(try to add '--skip-broken' to skip uninstallable packages or
'--nobest' to use not only best candidate packages)

Please consider that the ti-cgt-pru-native works without any flaws.
What have I made wrong? What can I do to make it works?

Thank you!

Ciao,
Alessio