Bug 12154

Summary:	esdk/devtool cannot build both native and target components
Product:	[Yocto Project Subprojects] eSDK	Reporter:	brian avery <brian.avery>
Component:	eSDK	Assignee:	Unassigned <unassigned>
Status:	NEW ---	QA Contact:	Francisco Pedraza <francisco.j.pedraza.gonzalez>
Severity:	normal
Priority:	Low	CC:	randy.macleod, sgw, wmills
Version:	2.4
Target Milestone:	Future
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description brian avery 2017-10-02 20:48:36 UTC

In the esdk, suppose i want to build a native and target version of a tool. I ran across this with ovmf and detailed part of that problem in Bug 12153.  In general however, I cannot build a target and native component.  

For example:
esdk$> devtool modify stat
# works
esdk$> devtool build stat
# works
esdk$> devtool build stat-native
ERROR: No recipe named 'stat-native' in your workspace
esdk$> devtool modify stat-native
ERROR: Another variant of recipe stat-native is already in your workspace (only one variant of a recipe can currently be worked on at once) 
## If I reset back and focus on the native one:
esdk$> devtool reset stat
esdk$> devtool modify stat-native
esdk$> devtool build stat-native
# works
esdk$> devtool build stat
ERROR: No recipe named 'stat' in your workspace
esdk$> devtool modify stat
ERROR: Another variant of recipe stat is already in your workspace (only one variant of a recipe can currently be worked on at once) 

++++++++++

As a further barrier to working with native tools, the script oe-run-native is not bundled with the esdk by default.

+++++
If working with native recipes/tools is out of scope for the esdk, please close this bug.

Comment 1 Paul Eggleton 2017-10-05 02:18:37 UTC

I'm aware of this issue, the tricky thing is that some recipes apply patches only for the native case or only for the target case, so it's hard to share a single source tree for those. We could of course only block (or show a warning for) recipes that do such things, but fixing this is not high on our current priority list.

Comment 2 Randy MacLeod 2025-07-03 15:32:51 UTC

Still worth doing when we have the people available. -- YP bug review.