Skip to content

zephyr-build-guide: define ZEPHYR_WORKSPACE before use #511

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

SurajSonawane2415
Copy link
Contributor

@SurajSonawane2415 SurajSonawane2415 commented Mar 6, 2025

ZEPHYR_WORKSPACE was not defined before use. This update ensures it is defined first, similar to how SOF_WORKSPACE is defined before use in "Build toolchains and SOF from sources".

I encountered this issue while building SOF with Zephyr using this document, where ZEPHYR_WORKSPACE was not defined. Defining ZEPHYR_WORKSPACE before use resolves the problem.

Testing

Generated the HTML documentation locally using:
make -C sof-docs VERBOSE=1 html

Screenshot from 2025-03-06 15-51-35

I would appreciate your review and any suggestions for improvement. Thank you!

@@ -31,6 +31,7 @@ Initialize the west manifest ``$ZEPHYR_WORKSPACE/sof/west.yml`` using the ``west

.. code-block:: bash

ZEPHYR_WORKSPACE=~/zephyr_workspace
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is usually defined as ~/work/sof/zephyr

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lgirdwood Yes you are correct! I looked into other build instructions, including build-from-scratch and build-with-docker to align the Zephyr path with this build guide—the correct path should be: ZEPHYR_WORKSPACE=~/work/sof/zephyr

ZEPHYR_WORKSPACE is not defined before use. Defining it first, as
done in 'Build toolchains and SOF from sources' where SOF_WORKSPACE
is defined before use.

Signed-off-by: Suraj Sonawane <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants