Re: [yocto] Downloading Git Archives
On 9/27/19 2:27 AM, Ross Burton wrote: > On 27/09/2019 05:33, Chuck Wolber wrote: >> I was hoping that there was an equally simple way of grabbing git >> repository packages from an Internet connected host without having a >> bitbake build cache them for me. > > The easy way is to get bitbake to do it for you. A git mirror tarball > is just a clone with a specific name and path, but the easy solution > is definitely to run bitbake --c fetchall on a machine with > connectivity and expose the DL_DIR to the builders. > > This is what the yocto autobuilder does, by the way. The workers > don't have connectivity to the outside internet, so the master does a > fetchall with the proxies configured to populate DL_DIR before the > workers do the actual build. > Same thing here. I run a build system instance that simply downloads all the sources and places them on a local mirror. The only thing to think about is that if you have different targets they might require different source packages albeit there is always a larger overlap of packages that are always required. However, it's not too big of a problem launching the 'fetcher' instance repeatedly with different target since only what's missing will of course be downloaded. Another layer of complexity is of course added if you work with different versions of YP and OE layers. I solve this with Gitlab and submodules. A target project is a repo in Gitlab and the YP/OE layers are submodules. Gitlab handles that quite nicely. :rjs - Rudolf J Streif CEO/CTO ibeeto +1.855.442.3386 x700 signature.asc Description: OpenPGP digital signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] kernel module and drivers missing in final image
On 27.09.2019 14:01, JH wrote: > Hi, > > I included emmy-w1-driver-sdiosdio in packagegroup.bb, but all drivers > and kernel modules in emmy-w1-driver-sdiosdio are missing in the > deploy image, any clues why, how to debug it, how to fix it? It is not clear to me what do you mean by including it in packagegroup.bb and what stuff are you installing into the image. If you wish to install all modules which were built, simply add kernel-modules to your image via IMAGE_INSTALL variable. > Thank you. > > Kind regards, > > - jh -- Maciej Pijanowski Embedded Systems Engineer GPG: F1401D2E1CCB19EF https://3mdeb.com | @3mdeb_com signature.asc Description: OpenPGP digital signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] kernel module and drivers missing in final image
Hi, I included emmy-w1-driver-sdiosdio in packagegroup.bb, but all drivers and kernel modules in emmy-w1-driver-sdiosdio are missing in the deploy image, any clues why, how to debug it, how to fix it? Thank you. Kind regards, - jh -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Downloading Git Archives
On 27/09/2019 05:33, Chuck Wolber wrote: I was hoping that there was an equally simple way of grabbing git repository packages from an Internet connected host without having a bitbake build cache them for me. The easy way is to get bitbake to do it for you. A git mirror tarball is just a clone with a specific name and path, but the easy solution is definitely to run bitbake --c fetchall on a machine with connectivity and expose the DL_DIR to the builders. This is what the yocto autobuilder does, by the way. The workers don't have connectivity to the outside internet, so the master does a fetchall with the proxies configured to populate DL_DIR before the workers do the actual build. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto Project new features survey
Hello, Yocto Project/Openembedded can nowadays be considered the 'de facto' standard among the automated generation systems of embedded linux distributions. Experienced users appreciate the features offered by Yocto Project and its complete customization that allows to adapt it to any specific requirement. However, from the beginner's point of view, the situation is a bit more complicated due to the Yocto Project's particularly steep learning curve. The tools that can support the development with Yocto Project are Toaster, that allow the configuration of the builds through a web interface, and the 'extended SDK' (eSDK), based on Devtool which allows the system to be tuned or extended without editing configuration files. Probably anyone who has tried to use Yocto Project will certainly have had the desire at least once to have a feature not available. For this reason it might be interesting to discuss it together. - What aspects of Yocto Project you consider not useful or misleading? - What functionality would you like to have in Yocto Project? - What do you think is missing? Take part to the survey at this link: http://bit.ly/2kXvdsd and let's continue this discussion at OEDAM and Yocto Project Summit 2019 P.S. if you think that can make sense to cross post this to OE mailing lists, feel free to share. If you think this is off-topic or doesn0t comply to any YP(OE ML polici, please ignore it and apologize me. -- Marco -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
