|
Re: How to write custom recipe to install AWS C SDK from github
#dunfell
#linux
#yocto
Hi Quentin Schulz & Ross,
Thanks for the information. Based on meta-aws I had written the recipe and do_compile has completed. Now I want to install demos in to the build which are located at
Hi Quentin Schulz & Ross,
Thanks for the information. Based on meta-aws I had written the recipe and do_compile has completed. Now I want to install demos in to the build which are located at
|
By
Vijay Rakesh Munganda
·
#51619
·
|
|
Re: #yocto
#yocto
Thanks you, this should help...
Thanks you, this should help...
|
By
Monsees, Steven C (US)
·
#51618
·
|
|
Re: How to write custom recipe to install AWS C SDK from github
#dunfell
#linux
#yocto
Hi VR,
You need to put the SDK filename into SRC_URI as well otherwise Yocto
does not fetch it from the files directory.
Also, Ross had a good suggestion too, please check that the recipe or
Hi VR,
You need to put the SDK filename into SRC_URI as well otherwise Yocto
does not fetch it from the files directory.
Also, Ross had a good suggestion too, please check that the recipe or
|
By
Quentin Schulz
·
#51617
·
|
|
Re: How to write custom recipe to install AWS C SDK from github
#dunfell
#linux
#yocto
Hi Quentin Schulz,
Thanks for the reply. I had downloaded the SDK into "files" folder of my recipe and given CMakeLists.txt as SRCURI. Is it correct to do like this?
Here is the Error: (It's a long
Hi Quentin Schulz,
Thanks for the reply. I had downloaded the SDK into "files" folder of my recipe and given CMakeLists.txt as SRCURI. Is it correct to do like this?
Here is the Error: (It's a long
|
By
Vijay Rakesh Munganda
·
#51616
·
|
|
Re: qt5 directory not creating using qt5.15.0 master branch
See QT_DIR_NAME variable in meta-qt5 and b716195f609de6547cfdfadfd4fd25292a6bbf09 commit which changed the default value.
See QT_DIR_NAME variable in meta-qt5 and b716195f609de6547cfdfadfd4fd25292a6bbf09 commit which changed the default value.
|
By
Martin Jansa
·
#51615
·
|
|
Re: How to write custom recipe to install AWS C SDK from github
#dunfell
#linux
#yocto
Hi VR,
If you don't give us the log, we won't be able to help you.
Where is the sdk? You need to add it into your SRC_URI (you can also
just pass a URL to a git repo or tarball download
Hi VR,
If you don't give us the log, we won't be able to help you.
Where is the sdk? You need to add it into your SRC_URI (you can also
just pass a URL to a git repo or tarball download
|
By
Quentin Schulz
·
#51614
·
|
|
Re: How to write custom recipe to install AWS C SDK from github
#dunfell
#linux
#yocto
I suggest looking at meta-aws (https://github.com/aws/meta-aws) to see
if that has a recipe already, and if it doesn't use one of the recipes
there as a starting point.
Ross
I suggest looking at meta-aws (https://github.com/aws/meta-aws) to see
if that has a recipe already, and if it doesn't use one of the recipes
there as a starting point.
Ross
|
By
Ross Burton <ross@...>
·
#51613
·
|
|
How to write custom recipe to install AWS C SDK from github
#dunfell
#linux
#yocto
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
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
|
By
Vijay Rakesh Munganda
·
#51612
·
|
|
Re: #yocto
#yocto
Hi Steve
lists.yoctoproject.org wrote:
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
Hi Steve
lists.yoctoproject.org wrote:
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
|
By
Nicolas Jeker
·
#51611
·
|
|
qt5 directory not creating using qt5.15.0 master branch
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
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
|
By
sateesh m
·
#51610
·
|
|
Re: Raspberry PI enabling MMC1
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,
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,
|
By
chuck kamas
·
#51609
·
|
|
Re: #yocto
#yocto
I still haven’t been able to track this down, can someone tell me in what package is the banner output generated ?
Thanks,
Steve
I still haven’t been able to track this down, can someone tell me in what package is the banner output generated ?
Thanks,
Steve
|
By
Monsees, Steven C (US)
·
#51608
·
|
|
Adding modules to Apache2 during build
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
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
|
By
mailings@...
·
#51607
·
|
|
Re: [docs] Yocto Project Technical Documentation Request For Quote
Good idea. I've done it now!
Good idea. I've done it now!
|
By
Nicolas Dechesne
·
#51606
·
|
|
Re: [docs] Yocto Project Technical Documentation Request For Quote
Should this be posted on the YP Jobs page?
-armin
Should this be posted on the YP Jobs page?
-armin
|
By
Armin Kuster
·
#51605
·
|
|
Yocto Project Status WW48'20
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
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
|
By
Stephen Jolley
·
#51604
·
|
|
Re: QA notification for completed autobuilder build (yocto-3.1.4.rc1)
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
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
|
By
Sangeeta Jain
·
#51603
·
|
|
hostapd_free_hapd_data: Interface wlan0 wasn't started
#linux
#kernel
#dunfell
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
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
|
By
Vijay Rakesh Munganda
·
#51602
·
|
|
Yocto Project Technical Documentation Request For Quote
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
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
|
By
Nicolas Dechesne
·
#51601
·
|
|
Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am on the first Tuesday (PDT)
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
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
|
By
Stephen Jolley
·
#51600
·
|