Put Yocto's development environment on Ubuntu.
I plan to put Yocto in other devices, but I don't know much about Yocto in the first place, so I would like to run a virtual Yocto using QEMU.
2020/09/04 Intel® Core™ i5-4570 CPU @ 3.20GHz × 4 Memory 32GB Ubuntu 20.04.1 LTS (64bit)
It may not work on Ubuntu on a virtual environment. Real environment is recommended.
sudo apt‑get install sed wget subversion git‑core coreutils \
unzip texi2html texinfo libsdl1.2‑dev docbook‑utils fop gawk \
python‑pysqlite2 diffstat make gcc build‑essential xsltproc \
g++ desktop‑file‑utils chrpath libgl1‑mesa‑dev libglu1‑mesa‑dev \
autoconf automake groff libtool xterm libxml‑parser‑perl
git clone https://git.yoctoproject.org/git/poky
When specifying the version ...
git checkout -b yocto-3.1 yocto-3.1
source poky/oe-init-build-env
bitbake core-image-minimal
Compile using 100% CPU4 core. It seems too strict to compile in a virtual environment.
It took 2 hours to compile.
runqemu tmp/deploy/images/qemux86-64/
The terminal has started. I see, is this Yocto?
I tried to find out what the default is.
User: root Pass: None
Hey.
Hey.
bitbake core-image-sato
Since sato is the minimum configuration (maybe) including GUI function, try compiling it.
runqemu tmp/deploy/images/qemux86-64/
Compiling ... 1 hour ... eh? Is core-image-sato faster than core-image-minimal? why? ??
So, Yocto started up using QEMU on Ubuntu. Chan Chan!
For the time being, I was able to build Yocto with the default settings, and then run it on QEMU. Knowing the compile time allows you to modify or change something I know how long I should wait.
However, it is unknown why minimal is slow (or sota is fast). What's the difference?
Well, the environment is ready for the time being. Will you learn how to use it? See you soon.
Recommended Posts