Add Troubleshooting for Linux and Windows to README #250
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
parasitepool/para!250
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/installation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Cheers ☕
After testing and assisting with several builds on both Linux and Windows, I've fleshed out details for two new troubleshooting sections - one for each OS, respectively. All official links are provided and embedded into the markdown with commands added where appropriate.
Some minor non-blocking nits.
Holding off on approving strictly for second opinion on windows section from paratoxic, but currently see no reason it shouldn't be approved.
@ -64,11 +64,11 @@ Setup### Requirements:@ -132,3 +132,31 @@ These versions can be verified with:rustc --versiongcc --versionStyle nit, I generally would avoid starting a list element with an inline codeblock.
Windows details look correct, but no windows environment available locally to validate, @paratoxicdev can you take a peak at this as well?
@ -132,3 +132,31 @@ These versions can be verified with:rustc --versiongcc --versionWe did the same thing here (attached), so I didn't think much of it, but I'll re-word it 👍🏼

Would love the confirmation; however, if it helps, I also went through this in a full installation tutorial as well:
https://www.youtube.com/watch?v=f8V2BSsor_I (02:56)
@ -132,3 +132,31 @@ These versions can be verified with:rustc --versiongcc --versionRe-worded to the following

@ -132,3 +132,31 @@ These versions can be verified with:rustc --versiongcc --versionYou are correct, I wonder why I didn't notice it there. Could be because of them being only version text after, will take a peek back at that :D
As odd as it sounds, this is actually a thing on Windows lol the MSVC option requires Visual Studio with Microsoft Build Tools (a VS package), and is literally defined as "Microsoft Visual C++". Rust will actually prompt you to install it when choosing this ABI, or tell you to install it yourself. It is mandatory to use one of these two ABIs if you're going to build with Rust on this OS. Welcome to Windows funsies 😜


If you watch the tutorial I made Installing Para, you can see the rust installer prompt you as mentioned above -> 03:34 timestamp. Here is a screenshot to verify it as well:
