-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve help for west build target #16202
Comments
The use of https://docs.zephyrproject.org/latest/getting_started/index.html#run-the-application-in-qemu
Several other usage examples are documented in the page for west build: https://docs.zephyrproject.org/latest/guides/west/build-flash-debug.html#basics
What exactly is missing here? The |
See also #5501 for a related open issue related to the QEMU devices. I didn't do it because I already faced enough backlash about "forcing" people to use west, and those targets have been special-cased and done their own thing since the Kbuild days. I think most of that pushback has been resolved, though, and I've heard from 4 people in the past month or so that they'd like to see more west integration with the runners, so I guess the "yeas" are starting to outvote the "nays" on this. |
I guess I'm hoping that the help we get from the tool is a bit more useful than having to go to online pages. |
The problem is that if we try to do that, the There are a lot of tools that make this tradeoff in my experience (short |
We have an open request to make the help for the -t option a little easier. Try to do that without adding too much length to the short help. Fixes: zephyrproject-rtos#16202 Signed-off-by: Martí Bolívar <[email protected]>
The current help for
west build -h
gets (fortarget
):It wasn't at all obvious at first reading what
target
meant here. Since this is Zephyr specific, I think it would be useful to have an example for how to invoke the 'run' target for qemu. (unfortunately double use of run)The text was updated successfully, but these errors were encountered: