On Tue, Oct 12, 2021 at 12:33 AM chuck kamas via
lists.yoctoproject.org <chuckkamas=yahoo.com@...>
wrote:
Thanks for the quick reply. I looked at the perf recipe, and its quite involved. Is there a simpler recipie to use as a template? Perhaps one of these?
My intent was just to show how you'd get the source from whatever
kernel you are building,
meta-openembedded/meta-oe/recipes-kernel/bpftool/bpftool.bb
meta-openembedded/meta-oe/recipes-kernel/spidev-test/spidev-test.bb
meta-openembedded/meta-oe/recipes-kernel/cpupower/cpupower.bb
all three of these appear to be basically the same very simple bb file.
Assuming that you don't need to patch the sources directly, any of
those would likely work ... depending on the dependencies and options
of what tool you are building.
Bruce
Chuck
On 10/11/21 5:46 PM, Bruce Ashfield wrote:
On Mon, Oct 11, 2021 at 6:16 PM chuck kamas via lists.yoctoproject.org
<chuckkamas=yahoo.com@...> wrote:
Hi all,
I've googled most of the day, but to no avail. How does one compile and
add to the image the daemon usbipd? Is there a bitbake file already for
this? The code is part of the kernel found in the kernel tree:
KERNEL_SRC_PATH/tools/usb/usbip/src
and is invoked from the KERNEL_SRC_PATH/tools directory by calling
make usb
from:
https://wiki.st.com/stm32mpu/wiki/How_to_build_Linux_kernel_user_space_tools
PC $> cd <Linux_kernel_source_path>/tools
PC $> make <tool>
I would think that there is a preexisting recipe.
There isn't one that I've ever heard of, and the layerindex
(http://layers.openembedded.org/) confirms that nothing registered
with it provides that recipe.
So if you need it, you'd have to create a recipe .. and submit it to
somewhere like meta-openembedded if appropriate.
Have a look at the perf recipe for one of the ways we build tools out
of the kernel source. Something similar will work in this case.
Bruce
thanks,
Chuck
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
