Hi Paul,
I saw your email on the gumstix list but forgot to "star" it, and
therefore didn't get back to it as I would have liked, sorry about
that.
I too play around with a gumstix from time to time, as well as other
boards. In my (still learning) opinion, the gumstix stable build is
based on really old stuff (i.e. from last... September? October?) So
in my case I tend to have two completely separate "yocto" areas: one
for gumstix, and another for everything else, and I don't mix anything
between the two except the download location. For example, the gumstix
build is sort of based on Danny, but not really, if you check, the
repositories are checked out at random points in time (detached HEAD
state) instead of actually using or tracking Danny.
Working with a gumstix is sort of like having to work with a vendor
branch: for best results you have to use their stuff, but their stuff
isn't really upstream or tracking upstream very closely. So it's best
not to confuse the "real" Yocto, for gumstix's Yocto-based build. For
example their instructions have you use the "repo" utility (instead of
just using git) and start your project with:
$ TEMPLATECONF=meta-gumstix/conf source ./poky/oe-init-build-env
instead of the "regular" template file and a regular git checkout of
the yocto project.
For best results I would recommend that you be sure to use a separate,
new terminal when you start your Intel work. That way various
environment variables (PATH, etc) don't interfere with each other.
As I mentioned above, you might get some savings if you open the
conf/local.conf of both projects and point the DL_DIR variable to the
same directory. But how much savings you'll get from that isn't
obvious (you might not get any).
Best regards,
Trevor
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
