On Wed, Jun 12, 2013 at 3:37 PM, Bryan Evenson <[email protected]> wrote: > # Added KBRANCH spec > KBRANCH = "linux-3.9-at91" >> > # Override SRC_URI in a bbappend file to point at a different source >> # >> > tree if you do not want to build from Linus' tree. >> > SRC_URI = "git://github.com/linux4sam/linux-at91.git;branch=linux- >> 3.9- >> at91;tag=dcdf169e24c0cb6d7dc69e0a09d2395934e95075;protocol=git;nochecko >> ut=1" > > # Changed SRC_URI to following > SRC_URI = > "git://github.com/linux4sam/linux-at91.git;branch=${KBRANCH};protocol=git;nocheckout=1"
It looks like all you did was to define the string "linux-3.9-at91" in its own variable, put that in your SRC_URI string, and remove the "tag=..." field. Would your original recipe have worked if all you did was remove the "tag=..." field? Is KBRANCH being used somewhere else? Doesn't bitbake's "git" fetcher already have a generic way of specifying a branch? Why would a kernel recipe need to also define a branch variable? Do non-kernel recipes also need to define some kind of branch variable too? _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
