Hi Philip, We have done this with many Yocto Project builds using AWS EC2, Docker, Gitlab and Artifactory. Rest inlined below. :rjs It can be configured that any check in to branches can trigger a bui

#yocto

The wording might need improvement but both of your examples actually do provide SRC_REV but in the inline form with SRC_URI (rev/tag). The documentation should probably say something like SRC_REV nee

Kent, Well that could be an internal git repository too. You weren't specific about that. SRC_URI can point anywhere you like which could also be tarball file: >>>>> DESCRIPTION = "Linux Kernel from T

Hi Kent, Create your own kernel recipe and provide a defconfig for it: SRC_URI += "file://defconfig" For example to build a bleeding kernel directly from Linus' repo: >>>>> DESCRIPTION = "Linux Kernel

Hi Phil, It looks like this is your first encounter with the Yocto Project. Welcome! You did not specify what USB hardware you are using hence I won't be able to give you a specific answer. To start,

Jeff, Looks like modpost was not built yet. Did you build the kernel first or at least ran bitbake virtual/kernel -c kernel_configme :rjs

Hi JH, The image root file system size is based on the actual content of the root file system. Besides ROOTFS_SIZE there are other variables that control how the root file system is sized: IMAGE_ROOTF

Hi, That's done via the extrausers class in an image recipe. Add this to your image recipe: >>>>>> inherit extrausers ROOT_PASSWORD = "secret" EXTRA_USERS_PARAMS = "usermod -p `openssl passwd ${ROOT_P

I suppose you just removed setting the PACKAGES variable from your recipe? You are including require recipes-qt/qt5/qt5.inc which redefines the PACKAGES variable adding a ${PN}-tools package that cons

Hi Berthold, Welcome to the Yocto Project. This line is the problem with your recipe: PACKAGES = "${PN}" This tells the build system to only create one package, the default package. Because this line

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 r

Chuck, Unless I am missing something (which I cannot entirely rule out), the default PREMIRRORS should actually do what you want. For the poky distro configuration has this: PREMIRRORS ??= "\ bzr://.*

Michael, You might want to share your recipe. Since do_install works on a private sysroot for your recipe it is unlikely that your module conflicts with a module with the same name from another recipe

Adding After=multi-user.target to the [Unit] section in your systemd service file should do what you want. :rjs

JH, To enable systemd service for your application your recipe needs to inherit the systemd class and install the service file in the proper directory. Here is what it should look like: inherit system

Hi Shravan, You need to checkout warrior from your meta-raspberrypi repo that you cloned. It looks as it is on the latest master. :rjs

You are very welcome. Enjoy working with YP. :rjs

Inlining below. Correct. If the source repo or the correct commit cannot be found from the PREMIRROR, bitbake will use SRC_URI from the recipe. You can block that behavior by setting BB_NO_NETWORK = "

Russell, That is exactly what devtool and the externalsrc class do. PREMIRROR is the wrong approach for that. :rjs

Hi Russell, devtool and eSDK are different things. The purpose of PREMIRRORS is to set a mirror for all recipes. It's a way for organizations to control where their YP builds download sources from. It