| Summary: | quilt not in OE-shell PATH | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Mehmet Bulut <mail> |
| Component: | Scripts and Tools | Assignee: | Christos Gavros <gavrosc> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | randy.macleod, richard.purdie, ross.burton, yoann.congal |
| Version: | 5.99 | ||
| Target Milestone: | 5.2 M2 | ||
| Hardware: | x86 | ||
| OS: | x86_64 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Mehmet Bulut
2024-11-26 16:57:19 UTC
Hi Mehmet, I tried to reproduce the behaviour you are describing. I am using ubuntu 22.04 as host machine where quilt (0.66) is already installed. So I followed the next steps in the host machine to modify helloworld recipe: -Switch to poky directory -Source oe-init-build-env -devtool modify helloworld -Switch to the ../build/workspace/sources/helloworld/oe-local-files -quilt new fix1.patch -quilt add helloworld.c -Making changes in helloworld.c -quilt refresh I didn’t notice any issue. Can you explain further how can I reproduce the issue? * Please bear with me , I am a newcomer :) Br Christos I think there is a bit of confusion here on my part, sorry. I was reading "Start an OE-shell" as being a devhell in recipe context. I think instead this refers to the "oe-init-build-env" command?
"devtool modify" doesn't create or drop you into a subshell so it is still in the main/parent context, not any specific recipe. Tools such as quilt are installed per recipe in ${WORKDIR}/recipe-sysroot-native via dependency so they can't be available in the parent context.
As such I'm not sure we can make quilt available in the original build context.
Whether we could have some simple command to place the user into the recipe context could be something to explore but also a lot more of a complex project.
Thx for looking into this Christos and thx for your comment Richard. As Richard pointed out, this originated from a misunderstanding between the two of us (which I seem to have caused by "inventing" the term OE-shell). I agree that it's not worth the hassle pursuing this further and suggest closing the ticket. Apologies again for the confusion and have a good time everyone! hi no worries at all :) ! Resolving as disucssed |