Skip to content
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

Order of installs for Windows is not specified #286

Open
gandalfas opened this issue Apr 15, 2023 · 3 comments
Open

Order of installs for Windows is not specified #286

gandalfas opened this issue Apr 15, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@gandalfas
Copy link

Issue Description

The Traditional Installation instructions for Windows on Getting Started do not specify the order of installs.

In my install, for various reasons, I chose to do the Traditional Install, even though I was installing 5.6.1. In that section there is no explicit step to install Swift after the dependencies, but under "Traditional", in the paragraph starting "Swift has been tested with VS 2019", the Download section was referenced before the big box describing the VS components. Because of that, with no other explicit ordering in the instructions, I installed Swift first, then proceeded to install the dependencies. This led to many problems.

Later I noticed that Swift should be installed as the last step. For example, in section "On Windows > Install using Scoop", installing Swift clearly follows installing the dependencies. And similarly, on page pwsacademy swift-setup, it says to install Swift after the dependencies.

Requested Change

This is for page Getting Started. Assuming that you will be keeping the Traditional Instructions for some time to come...

1. In section: Installing Swift > On Windows > Installation Instructions > Traditional Installation:

change this:
Swift has been tested with Visual Studio 2019. You will need to install Visual Studio with the following components. <<The installer for Swift is available in the Download section. The toolchain on Windows is installed to %SystemDrive%\Library\Developer\Toolchains.>>

to this:

Swift has been tested with Visual Studio 2019. You will need to install Visual Studio with the following components.

.
2. Then just below, insert the following, just above 'Support Files', in order to place it right at the spot you need it (these details are akin to the macOS notes above):

Next install Swift. The installer for Swift is available in the Download section.

The toolchain on Windows is installed to %SystemDrive%\Library\Developer\Toolchains.

This install creates the env var:
SDKROOT=C:\Library\Developer\Platforms\Windows.platform\Developer\SDKs\Windows.sdk

and it adds three directories to the end of the PATH env var:
C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin
C:\Library\Swift-development\bin
C:\Library\icu-69.1\usr\bin

.
3. In Support Files, change this sentence:

You must use the x64 Native Tools for VS2019 Command Prompt to run the following steps.

to this:

You must use the x64 Native Tools for VS2019 Command Prompt, run as Administrator, to run the following steps.

Related Issue

This was originally submitted as 58451.

Environment details

Desktop

  • OS: Windows 10 desktop computer
  • Version: Swift 5.6.1
@gandalfas gandalfas added the bug Something isn't working label Apr 15, 2023
@gandalfas
Copy link
Author

gandalfas commented Sep 14, 2023

@shahmishal and @kaishin, in the massive work done in #354 (and THANKS for all that effort!!), I was hoping my items 1 and 2 described above might be addressed (item 3 was addressed, and thanks for that!).

Could it be that my error (not installing dependencies first) is rare because most people would just know that? (I described what led me to that in my second paragraph, at the top).

I'd appreciate your thoughts. Please excuse any wrong expectations, I am new to many github procedures. If you are not the appropriate people to ask, please send guidance on that.

Thanks!

@alexandersandberg
Copy link
Collaborator

@gandalfas we are soon merging some improvements to the Windows instructions in #385. Would be great if you could take a look at those changes to see if you're still having issues. 🙂

@gandalfas
Copy link
Author

@alexandersandberg, thanks, I will!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants