|
same build for multiple machine configurations
Alexandru Ionita
Hello all, I'm not sure if this is even possible at all. I'm using the meta-raspberry layer to build raspberry images. Whilst I'm able to build images by strictly selecting a raspberry pi machine configuration (MACHINE=raspberrypi3), I would like to know if it's possible to build an image that is compatible with multiple raspberry pi machine configurations. For instance an image that would work for both raspberrypi3 and raspberrypi4. Thanks. Alex
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: [OE-core] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.14.rc1)
Richard Purdie
On Tue, 2022-02-15 at 12:46 +0000, Teoh, Jay Shen wrote:
Hi All,Thanks for testing! The TSC did discuss this today and agreed it should be good to release. Cheers, Richard
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Yocto Project Status WW07`22
Stephen Jolley
Current Dev Position: YP 3.5 M3 Next Deadline: 21th Feb. 2022 YP 3.5 M3 build
Next Team Meetings:
Key Status/Updates:
In particular, we’re struggling to understand the intermittent network issue with external hosts we’re seeing very occasionally.
Ways to contribute:
YP 3.5 Milestone Dates:
Upcoming dot releases:
Tracking Metrics:
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@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
gpsd bbappend adding new file causing QA errors even with FILES_${PN}:append set
mattwood2000@...
Hi,
I've seen many questions about this with proposed answers but I cannot seem to get this to work for my bbappend to gpsd. I'm simply trying to add an additional systemd service file I created for the gpspipe client. What is strange is that I'm already appending the ${systemd_system_unitdir} in this bbappend to replace gpsd.socket with no error. I'm confused why adding one additional file to a directory that is already being appended could cause the QA error: ERROR: gpsd-3.23.1-r0 do_package: QA Issue: gpsd: Files/directories were installed but not shipped in any package: /lib/systemd/system/gpspipe.service The recipe is below - I've commented out the three lines that cause the error. Anyone have any ideas why this is happening? Thanks, Matt. gpsd_%.bbappend: FILESEXTRAPATHS:prepend := "${THISDIR}/files:" SRC_URI += "\ file://gpsd.default \ file://gpsd.socket \ file://gpspipe.service \ " inherit systemd SYSTEMD_PACKAGES = "${PN}" SYSTEMD_AUTO_ENABLE = "enable" SYSTEMD_SERVICE_${PN}:append = " gpsd.service gpsd.socket gpspipe.service " do_install:append () { install -d ${D}${sysconfdir}/default/ install -d ${D}${sysconfdir}/systemd/system/multi-user.target.wants/ install -d ${D}${sysconfdir}/systemd/system/sockets.target.wants/ install -D -m 600 ${WORKDIR}/gpsd.default ${D}${sysconfdir}/default/ install -D -m 600 ${WORKDIR}/gpsd.socket ${D}${systemd_system_unitdir} # install -D -m 600 ${WORKDIR}/gpspipe.service ${D}${systemd_system_unitdir} ln -s ${systemd_unitdir}/system/gpsd.service ${D}${sysconfdir}/systemd/system/multi-user.target.wants/gpsd.service ln -s ${systemd_unitdir}/system/gpsd.socket ${D}${sysconfdir}/systemd/system/sockets.target.wants/gpsd.socket # ln -s ${systemd_unitdir}/system/gpspipe.service ${D}${sysconfdir}/systemd/system/multi-user.target.wants/gpspipe.service } FILES_${PN}:append = " \ ${sysconfdir}/systemd/system/multi-user.target.wants \ ${sysconfdir}/systemd/system/sockets.target.wants \ ${sysconfdir}/default/gpsd.default \ ${systemd_system_unitdir}/gpsd.socket \ # ${systemd_system_unitdir}/gpspipe.service \ "
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Best laptop for compiling Yocto
Greg Wilson-Lindberg
Hello All, I have a System 76 Serval laptop that I have been using when building Yocto. It seems to be dying and they are on back order now, so not available for replacement. I was wondering what recommendations others would have for a good laptop to use for building Yocto?
Regards, Greg
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: [linux-yocto] Controlling features enable/disable across recipe and meta layers ?
Alexander Kanavin
You need to define several distributions (e.g. several
toggle quoted messageShow quoted text
conf/distro/something.conf files), then you can set DISTRO_FEATURES accordingly in each of them, and then on the recipe level PACKAGECONFIGs can be enabled subject to DISTRO_FEATURES. Note that each of those .conf files can include the same .inc, where the common parts go, and only differ in things that need to be different. Yocto does not provide a way to have different 'products' or 'builds' inside the same distro: you choose a distro, then you choose a target MACHINE (e.g. the hardware), then you choose the image to build. Also, distro definitions do not belong in a BSP layer, they need to go to a separate distro layer. You can ask your colleagues at QC how this was cleaned up for a certain big german automotive customer and look at the resulting layer code. Alex
On Tue, 15 Feb 2022 at 16:05, Pintu Agarwal <pintu.ping@...> wrote:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Controlling features enable/disable across recipe and meta layers ?
Pintu Agarwal
Hi,
I have many questions about Yocto features. My main question is: In Yocto what is the best mechanism to define a feature flag such that it can be accessed across many layers and recipes ? We are using Yocto thud and/or dunfell at this moment for 2 different products. From the Yocto document also it is not very clear which one to use. Also, we are confused when one to use when, like we have: DISTRO Feature flag, PACKAGECONFIG variable, IMAGE Feature, Global Macro (setVar, getVar), etc. Example: Currently, we have many different releases and many different products use it. So, we have many distro features, many of them are common and many of them we defined newly for our product. But for our product we have only one component (say: auto-prod). So, when this component is enabled the same release should be built for our product including our feature set. And when this component is disabled, all our features should be disabled like mainline release. So, we wanted to define only one DISTRO feature (auto-prod) and list all our features under this distro. Also we wanted to control all these from a single place, so that enabling/disabling all the features in one shot would be easy and portable. We tried doing it using PACKAGECONFIG but it seems this option can be used only at a recipe level and not visible across all layers. We wanted to do something like this in: auto.conf DISTRO_FEATURES = "auto-prod" if defined (distro-features == auto-prod) ; then PACKAGECONFIG_append-pn-<recipe1> = "f1 f2 ..." PACKAGECONFIG_append-pn-<recipe2> = "f2 f3 ..." PACKAGECONFIG_append-pn-<recipe3> = "f1 f3 f4..." fi So, if we comment DISTRO_FEATURES all the features listed above should be automatically disabled. Note, our feature flags are used across multiple recipes and layers. Bootloader layer, Kernel, meta layer, recipe layer, python source, C source, scripts, etc. Like: edk2, meta-qti-bsp, meta-security, meta-qti-auto, auto-prod-folder, etc. Is there a well defined way in Yocto to achieve such a modular design approach ? If there are any such references please share. Our reference distro is here: https://source.codeaurora.org/quic/le/meta-qti-bsp/tree/conf/distro/auto.conf?h=yocto.lnx.3.0.c28 Thanks, Pintu
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.14.rc1)
Teoh, Jay Shen
Hi All,
toggle quoted messageShow quoted text
This is the full report for yocto-3.1.14.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high milestone defects. No new issue found. Thanks, Jay
-----Original Message-----
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-3.4.2.rc2)
Teoh, Jay Shen
Hi all,
toggle quoted messageShow quoted text
Intel and WR YP QA is planning for QA execution for YP build yocto-3.4.2.rc2. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. Coffee Lake 3. NUC 7 4. NUC 6 5. Edgerouter 6. Beaglebone ETA for completion this Friday, Feb 18. Thanks, Jay
-----Original Message-----
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
M+ & H bugs with Milestone Movements WW07
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Enhancements/Bugs closed WW07!
Stephen Jolley
All,
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.5
Stephen Jolley
All,
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
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 401 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.5, “3.6”, "3.99" and "Future", the more pressing/urgent issues being in "3.4" and then “3.5”.
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@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: [meta-hardening][PATCH] meta-hardening: Fix override syntax
On 2/14/22 09:05, Akshay Bhat wrote:
On Fri, Jan 21, 2022 at 11:33 AM Akshay Bhat <nodeax@...> wrote:Thanks for the ping. I didn't find this in my inbox but found it on lore mailing list.Commit 352e6498a missed updating the override syntax for thePing... any feedback on the patch? If not can it be applied? Thanks :) Patch looks fine. thanks, -armin
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
QA notification for completed autobuilder build (yocto-3.4.2.rc2)
Pokybuild User <pokybuild@...>
A build flagged for QA (yocto-3.4.2.rc2) was completed on the autobuilder and is available at:
https://autobuilder.yocto.io/pub/releases/yocto-3.4.2.rc2 Build hash information: bitbake: c039182c79e2ccc54fff5d7f4f266340014ca6e0 meta-agl: 1a8abc70c4f2339200b612d96d81c4eec3ac0519 meta-arm: 51b728a52bde7c613d5855afeac0fa6a31771bd2 meta-aws: c92344938ab4d37de8bd8b799186dbbe3019a069 meta-gplv2: f04e4369bf9dd3385165281b9fa2ed1043b0e400 meta-intel: 5a30dcefa54040dd05099549a56156a83263554c meta-mingw: f5d761cbd5c957e4405c5d40b0c236d263c916a8 meta-openembedded: c05ae80ba680887ac924c21536091be7a1173427 oecore: 418a9c4c31615a9e3e011fc2b21fb7154bc6c93a poky: e0ab08bb6a32916b457d221021e7f402ffa36b1a This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.purdie@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Additional hardening options
Bernhard Rosenkränzer <bero@...>
Hi,
On Wed, Jan 26, 2022 at 02:39 AM, Paul Eggleton wrote: I've been looking into a couple of compiler flags for hardening that I think weI've been looking into those flags (and a few more) a while back when picking compiler flags to use for Oniro. -Wl,-z,-noexecstack is unproblematic, -fstack-clash-protection adds a bit of overhead, but it isn't all that bad (typically in the 2% range). I've been able to build working systems with both flags enabled. My full report is at https://forum.ostc-eu.org/t/compiler-flags-to-be-used-for-all-scenarios-os/94 ttyl bero
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Building Yocto on M1 Mac
Robert Joslyn
On Feb 14, 2022, at 4:02 AM, Ross Burton <ross@...> wrote:Giving docker all 16 GB of memory made the build take 124 minutes. I assume this is due to the VM docker uses fighting for memory with the build and the host, slowing things down. I’m sure someone could find an optimal amount of memory to give the docker VM for best times. I did these builds with the MBA on its side, which should be a little better than it just being flat on a desk (or sitting on pencils). A fan would also help, but lack of a fan is one of my favorite features! This was also done at room temperature, 68 F/20 C, I’m sure it’d be a bit faster if I went outside where it’s below freezing, but I’ll let someone else run that test :-D The MBA is obviously not intended for this kind of workload, but it does at least work. Robert
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[meta-security-compliance][PATCH] scap-security-guide: Fix openembedded platform tests
Akshay Bhat
Update the installed_OS_is_openembedded check to drop the quotes
in the VERSION_ID string to match f451c68667cca of openembedded-core. Without this fix, all tests are reported as "notapplicable". Signed-off-by: Akshay Bhat <akshay.bhat@...> --- ...is_openembedded-Update-pattern-match.patch | 30 +++++++++++++++++++ .../scap-security-guide_git.bb | 1 + 2 files changed, 31 insertions(+) create mode 100644 meta-security-compliance/recipes-openscap/scap-security-guide/files/0001-installed_OS_is_openembedded-Update-pattern-match.patch diff --git a/meta-security-compliance/recipes-openscap/scap-security-guide/files/0001-installed_OS_is_openembedded-Update-pattern-match.patch b/meta-security-compliance/recipes-openscap/scap-security-guide/files/0001-installed_OS_is_openembedded-Update-pattern-match.patch new file mode 100644 index 0000000..61d9206 --- /dev/null +++ b/meta-security-compliance/recipes-openscap/scap-security-guide/files/0001-installed_OS_is_openembedded-Update-pattern-match.patch @@ -0,0 +1,30 @@ +From d943e41d64da6af89a6b8224110299ad88747497 Mon Sep 17 00:00:00 2001 +From: Akshay Bhat <akshay.bhat@...> +Date: Mon, 14 Feb 2022 13:00:31 -0500 +Subject: [PATCH] installed_OS_is_openembedded: Update pattern match + +The VERSION_ID string is no longer quoted with f451c68667cca of +openembedded-core. Update the pattern match check in +installed_OS_is_openembedded to match the same. + +Signed-off-by: Akshay Bhat <akshay.bhat@...> +--- + shared/checks/oval/installed_OS_is_openembedded.xml | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/shared/checks/oval/installed_OS_is_openembedded.xml b/shared/checks/oval/installed_OS_is_openembedded.xml +index 01df16b43..eaf9f2b10 100644 +--- a/shared/checks/oval/installed_OS_is_openembedded.xml ++++ b/shared/checks/oval/installed_OS_is_openembedded.xml +@@ -23,7 +23,7 @@ + </ind:textfilecontent54_test> + <ind:textfilecontent54_object id="obj_openembedded" version="1" comment="Check OpenEmbedded version"> + <ind:filepath>/etc/os-release</ind:filepath> +- <ind:pattern operation="pattern match">^VERSION_ID=\"nodistro\.[0-9].$</ind:pattern> ++ <ind:pattern operation="pattern match">^VERSION_ID=nodistro\.[0-9]$</ind:pattern> + <ind:instance datatype="int">1</ind:instance> + </ind:textfilecontent54_object> + +-- +2.25.1 + diff --git a/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide_git.bb b/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide_git.bb index ddde5cc..f493ea8 100644 --- a/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide_git.bb +++ b/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide_git.bb @@ -9,6 +9,7 @@ SRC_URI = "git://github.com/akuster/scap-security-guide.git;branch=oe-0.1.44;;pr file://0003-fix-remaining-getchildren-and-getiterator-functions.patch \ file://0001-Fix-platform-spec-file-check-tests-in-installed-OS-d.patch \ file://0002-Fix-missing-openembedded-from-ssg-constants.py.patch \ + file://0001-installed_OS_is_openembedded-Update-pattern-match.patch \ " PV = "0.1.44+git${SRCPV}" -- 2.25.1
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
QA notification for completed autobuilder build (yocto-3.4.2.rc2)
Richard Purdie
A build flagged for QA (yocto-3.4.2.rc2) was completed on the autobuilder and is
available at: https://autobuilder.yocto.io/pub/releases/yocto-3.4.2.rc2 Build hash information: bitbake: c039182c79e2ccc54fff5d7f4f266340014ca6e0 meta-agl: 1a8abc70c4f2339200b612d96d81c4eec3ac0519 meta-arm: 51b728a52bde7c613d5855afeac0fa6a31771bd2 meta-aws: c92344938ab4d37de8bd8b799186dbbe3019a069 meta-gplv2: f04e4369bf9dd3385165281b9fa2ed1043b0e400 meta-intel: 5a30dcefa54040dd05099549a56156a83263554c meta-mingw: f5d761cbd5c957e4405c5d40b0c236d263c916a8 meta-openembedded: c05ae80ba680887ac924c21536091be7a1173427 oecore: 418a9c4c31615a9e3e011fc2b21fb7154bc6c93a poky: e0ab08bb6a32916b457d221021e7f402ffa36b1a This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.purdie@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
ksmanjunath681@...
Hi,
i am trying to update bbappend files only with SRCREV, SRCBRANCH and SRC_URI defined in bbappend files using devtool .What should i follow Thanks & regards, Manjunath
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|