-
Notifications
You must be signed in to change notification settings - Fork 7.4k
doc: notes for sdk installation in shared environments #81615
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
doc: notes for sdk installation in shared environments #81615
Conversation
6814414
to
b0697dd
Compare
This comment has been minimized.
This comment has been minimized.
d2a53b3
to
8cc69b3
Compare
8cc69b3
to
703fed9
Compare
@kartben @stephanosio - Please take a look again when you have some time. |
703fed9
to
daa7461
Compare
@ycsin, @stephanosio, @kartben - please take another look. Docs should be fine. I'm not sure what's up with CI at the moment otherwise. |
Add an anchor for installing the Zephyr SDK in the main page of the Getting Started Guide. Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
In the SDK documentation, add some notes for those who wish to install the Zephyr SDK and Python virtual environment in shared or distributed build environments. Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
Include notes in the Zephyr SDK doc for those who wish to build redistributable files for package managers (e.g. APT, RPM). This does not mean that Zephyr will be responsible for creating collections of .deb or .rpm packages for the Zephyr SDK. These are only some guidelines based on previous experience in that area. Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
daa7461
to
edbdec5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies for having completely dropped the ball on this PR
To me these are "tips" that are not really something that belongs to the Zephyr documentation. Maybe something for a blog post?
How to manage python venvs is really out of scope IMO just like we don't have, I don't know, instructions on how to setup a ramdisk to speed up compilation or whatever.
agree, I have loads of tips/tricks and best practices for doing things with zephyr, does not mean they should be part of the docs. Blog is probably an overkill, maybe we could add a section in the wiki for "Best Known Methods (BKM)" where such info can live. |
Doc Preview