Mailing it to the thread. -----Original Message----- From: Tg, Harish Sent: Friday, May 24, 2019 11:17 AM To: Khem Raj <raj.k...@gmail.com>; yocto@yoctoproject.org Subject: RE: [yocto] EXT SENDER - yocto Digest, Vol 104, Issue 95
Hi Raj, What I am asking you is that how the yocto picks up components for /usr/bin folder of rootfs. Where do they exist before copying? I am sorry but I feel I do not need to write a recipe for adding just one of the commands. It is just that I need to add "ubiattach" to target /usr/bin of rootfs. That’s why I am asking where do I place my "ubiattach" command and there should also be a folder for this. Please clarify. Thanks, Harish. -----Original Message----- From: Khem Raj [mailto:raj.k...@gmail.com] Sent: Friday, May 24, 2019 11:03 AM To: Tg, Harish <harish...@aptiv.com>; yocto@yoctoproject.org Subject: Re: [yocto] EXT SENDER - yocto Digest, Vol 104, Issue 95 Please keep the thread on list and avoid pm. as I said you need 1. Write a recipe for your package 2. in do_install of the recipe you want to mention where it should be placed e.g. install -D -m 0755 <your-binary> ${D}${bindir}/<your-binary> would put it in /usr/bin on target when this package is included in image 3. Include the package in image via IMAGE_INSTALL On 5/23/19 10:13 PM, Tg, Harish wrote: > Hi Raj, > Another question I have is where do I place my custom > "ubiattach" command. Also I am not sure from where does the yocto builds the > rootfs /usr/bin components. Where do they copied from? > > Thanks, > Harish. > > -----Original Message----- > From: Khem Raj [mailto:raj.k...@gmail.com] > Sent: Friday, May 24, 2019 7:07 AM > To: Tg, Harish <harish...@aptiv.com>; yocto@yoctoproject.org > Subject: Re: [yocto] EXT SENDER - yocto Digest, Vol 104, Issue 95 > > > > On 5/23/19 5:59 AM, Tg, Harish wrote: >> Hi, >> I have a question. How to add commands like "ubiattach" to /usr/bin >> of rootfs image. I struggling with the recipes. I do not want to write my >> own recipe but I need to edit some recipe and add the command. Which is the >> place? I am using yocto for my project on TI platform and Linux. >> Kindly help. >> > > There is oe-pkgdata-util which can help to map files to recipes but we > do not have a database for mapping. Maybe it is a good thing to have > > for your problem ubiattach is provided by mtd-utils-ubifs which is > built from mtd-utils recipe. I found it via above tool > > % oe-pkgdata-util find-path /usr/sbin/ubiattach.mtd-utils > mtd-utils-ubifs: /usr/sbin/ubiattach.mtd-utils > > % oe-pkgdata-util lookup-recipe mtd-utils-ubifs mtd-utils > > So you need to add > > IMAGE_INSTALL_append = " mtd-utils-ubifs" in your image recipe or > local.conf >> >> Thanks, >> Harish. >> >> -----Original Message----- >> From: yocto-boun...@yoctoproject.org >> [mailto:yocto-boun...@yoctoproject.org] On Behalf Of >> yocto-requ...@yoctoproject.org >> Sent: Wednesday, May 22, 2019 6:57 PM >> To: yocto@yoctoproject.org >> Subject: EXT SENDER - yocto Digest, Vol 104, Issue 95 >> >> Send yocto mailing list submissions to >> yocto@yoctoproject.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoproje >> c >> t.org_listinfo_yocto&d=DwICAg&c=QM_z7khAIdagwHt-12JlKA&r=4dfUpqj68eYA >> f >> VJs5uk2XkolcOQysOP5VncSFx6bkao&m=swLBJyRzgqx-Ix1dnv04ZhN6a_WVQSmQSW5Y >> Y Lg3h40&s=a4sSVLnzzAP3ZRYs01WvSaiSc9QQmfaT7zdBRe0HcwM&e= >> or, via email, send a message with subject or body 'help' to >> yocto-requ...@yoctoproject.org >> >> You can reach the person managing the list at >> yocto-ow...@yoctoproject.org >> >> When replying, please edit your Subject line so it is more specific than >> "Re: Contents of yocto digest..." >> >> >> Today's Topics: >> >> 1. GPLv3 package present in rootfs (virendra kumar thakur) >> 2. Building single package as image, respecting dependencies >> (Norman Stetter) >> >> >> --------------------------------------------------------------------- >> - >> >> Message: 1 >> Date: Wed, 22 May 2019 18:55:45 +0530 >> From: virendra kumar thakur <coolvee...@gmail.com> >> To: yocto@yoctoproject.org >> Subject: [yocto] GPLv3 package present in rootfs >> Message-ID: >> <CANGFfGamnoJ-YB=m7cvn4xbwiey8v53s+prfg00e1-awwqz...@mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" >> >> Hello team, >> >> I want to remove some GPLv3 package from rootfs, but it is still present. >> >> I am using INCOMPATIBLE_LICENSE = "GPL-3.0 LGPL-3.0 AGPL-3. 0" >> >> still some package gnutls, libidn2, libassuan, are added into rootfs. >> -------------- next part -------------- An HTML attachment was >> scrubbed... >> URL: >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.yoctoproje >> c >> t.org_pipermail_yocto_attachments_20190522_fb9ebe67_attachment-2D0001. >> html&d=DwICAg&c=QM_z7khAIdagwHt-12JlKA&r=4dfUpqj68eYAfVJs5uk2XkolcOQy >> s >> OP5VncSFx6bkao&m=swLBJyRzgqx-Ix1dnv04ZhN6a_WVQSmQSW5YYLg3h40&s=BBPanV >> h jmdOQaYXZFeb4RWi9MdRpGYBFLmqihDeSAds&e=> >> >> ------------------------------ >> >> Message: 2 >> Date: Wed, 22 May 2019 12:36:18 +0000 >> From: Norman Stetter <norman.stet...@garz-fricke.com> >> To: "yocto@yoctoproject.org" <yocto@yoctoproject.org> >> Subject: [yocto] Building single package as image, respecting >> dependencies >> Message-ID: >> >> <a24dc035fe5f8f4bae7f63fb1b07d7bc532...@srv24.hamburg.garz-fricke.de> >> Content-Type: text/plain; charset="iso-8859-1" >> >> Hi there, >> >> I am currently working on a minimal CLI only system. >> The image is based on 'core-image-base' using sysvinit and busybox. >> To reduce image size and boot time, I removed as many packages as possible. >> For some application cases I will need python3 though. >> My idea was to have python3 as some kind of add-on in a squashfs image, that >> can be mounted only when needed. >> >> So I tried to build an image only containing the python3 package, but as >> little as possible otherwise, like this: >> >> inherit image >> IMAGE_FSTYPES = "squashfs-xz" >> DEFAULT_TASK_PROVIDER = "" >> DISTRO_EXTRA_RDEPENDS = "" >> DISTRO_FEATURES = "" >> POKY_DEFAULT_EXTRA_RDEPENDS = "" >> IMAGE_FEATURES = "" >> IMAGE_LINGUAS = "" >> CORE_IMAGE_BASE_INSTALL = "" >> RDEPENDS_${PN} = "" >> PACKAGE_EXCLUDE = "busybox openssl run-postinsts update-rc.d" >> VIRTUAL-RUNTIME_dev_manager = "" >> VIRTUAL-RUNTIME_login_manager = "" >> VIRTUAL-RUNTIME_init_manager = "" >> VIRTUAL-RUNTIME_initscripts = "" >> VIRTUAL-RUNTIME_keymaps = "" >> VIRTUAL-RUNTIME_base-utils = "" >> PREFERRED_PROVIDER_virtual/base-utils = "" >> >> IMAGE_INSTALL = "python3" >> >> But like this I can only manually exclude packages I already have in my main >> OS image. Some packages can't be excluded at all, as python3 depends on them >> and won't build if they are excluded. >> >> Is there a way to have dependencies between images? So I could have the >> python-image build know which dependencies are already built into my OS >> image and therefore not include them itself? >> >> Or would it be better to avoid building a second image and rather build >> 'python3' with my OS-image, adding it to PACKAGE_EXCLUDE and from within >> this build process pack all python3 files into an image? If I were to pursue >> this method, any suggestions on how to separate the python3 files from the >> rest of my rootfs, including the necessary dependencies? >> >> Any advice and idea is much appreciated. >> >> Mit freundlichen Gr??en / Best regards Norman Stetter SW ENWICKLUNG >> EMBEDDED SYSTEMS Garz & Fricke GmbH >> >> 21079 Hamburg >> Direct: +49 40 791899 - 477 >> Fax: +49 40 791899 - 39 >> norman.stet...@garz-fricke.com >> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.garz-2Dfricke. >> com&d=DwICAg&c=QM_z7khAIdagwHt-12JlKA&r=4dfUpqj68eYAfVJs5uk2XkolcOQys >> O >> P5VncSFx6bkao&m=swLBJyRzgqx-Ix1dnv04ZhN6a_WVQSmQSW5YYLg3h40&s=fl8zX_T >> 7 >> 4tP17S2Md1xvMmXVmWrPLjwZO929euOi-f4&e=<https://urldefense.proofpoint. >> com/v2/url?u=https-3A__urldefense.proofpoint.c&d=DwICaQ&c=QM_z7khAIda >> gwHt-12JlKA&r=4dfUpqj68eYAfVJs5uk2XkolcOQysOP5VncSFx6bkao&m=tVv1rujcV >> uvVSfL6k8LnHebpK0ebdIKd-dlegsAocXg&s=3TxoSarkI3yWxgR-_Jv5_iQxXSqXHm4u >> v9XDVtSEqXY&e= >> om/v2/url?u=http-3A__www.garz-2Dfricke.com_&d=DwICAg&c=QM_z7khAIdagwH >> t >> -12JlKA&r=4dfUpqj68eYAfVJs5uk2XkolcOQysOP5VncSFx6bkao&m=swLBJyRzgqx-I >> x >> 1dnv04ZhN6a_WVQSmQSW5YYLg3h40&s=jJytG_UXo6f8Dg1w9Rx7ZBrPvaIZd6dT0SEaT >> M >> hqRpw&e=> >> WE MAKE IT YOURS! >> [cid:image001.jpg@01D510A9.7F9CD640] >> Sitz der Gesellschaft: D-21079 Hamburg >> Registergericht: Amtsgericht Hamburg, HRB 60514 >> Gesch?ftsf?hrer: Matthias Fricke, Manfred Garz, Marc-Michael Braun >> >> -------------- next part -------------- An HTML attachment was >> scrubbed... >> URL: >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.yoctoproje >> c >> t.org_pipermail_yocto_attachments_20190522_063fd326_attachment.html&d >> = >> DwICAg&c=QM_z7khAIdagwHt-12JlKA&r=4dfUpqj68eYAfVJs5uk2XkolcOQysOP5Vnc >> S >> Fx6bkao&m=swLBJyRzgqx-Ix1dnv04ZhN6a_WVQSmQSW5YYLg3h40&s=nJpIij2wJ-ToI >> 1 >> 3ns1riHcQrZ9SCYkkyh-eRg-FKydE&e=> >> -------------- next part -------------- A non-text attachment was >> scrubbed... >> Name: image001.jpg >> Type: image/jpeg >> Size: 14804 bytes >> Desc: image001.jpg >> URL: >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.yoctoproje >> c >> t.org_pipermail_yocto_attachments_20190522_063fd326_attachment.jpg&d= >> D >> wICAg&c=QM_z7khAIdagwHt-12JlKA&r=4dfUpqj68eYAfVJs5uk2XkolcOQysOP5VncS >> F >> x6bkao&m=swLBJyRzgqx-Ix1dnv04ZhN6a_WVQSmQSW5YYLg3h40&s=uyxqA24JcBr0zB >> h >> HwTfA8XtqX5ObrRkNMFNlD3Htpos&e=> >> >> ------------------------------ >> >> -- >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoproje >> c >> t.org_listinfo_yocto&d=DwICAg&c=QM_z7khAIdagwHt-12JlKA&r=4dfUpqj68eYA >> f >> VJs5uk2XkolcOQysOP5VncSFx6bkao&m=swLBJyRzgqx-Ix1dnv04ZhN6a_WVQSmQSW5Y >> Y Lg3h40&s=a4sSVLnzzAP3ZRYs01WvSaiSc9QQmfaT7zdBRe0HcwM&e= >> >> >> End of yocto Digest, Vol 104, Issue 95 >> ************************************** >> -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto