Create Extended Guide#5
Open
Killy728 wants to merge 2 commits into
Open
Conversation
Polypheides
reviewed
Feb 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is my proposed extended guide to helpfully help folks who aren't super familiar with the terminal or Linux environment. With DSpico becoming more and more mainstream, the value of this resource may not be as important compared to when I first wrote it.
Whether or not it is valuable is up to the maintainers.
I recommend that it be looked over for accuracy, as I, myself, am not too familiar with the Terminal or Linux environment. I do know the steps work, as I was able to compile firmware reliably with the steps I had.
I had to reformat my original document to conform to GitHub's different markdown notation (compared to Notepad++), so hopefully it is legible, and I translated everything correctly.
I originally had it as a "For Dummies" guide as a nod to the product, but I can see that that title could be misinterpreted. Sticking with an "Extended Guide" may be the best. I'll leave that final decision to whoever.
I am also very new to doing any sort of work on GitHub, so I hope this is the correct way to do what I did.