Windows and WSL #111
Labels
Comments
Techatrix
added a commit
that referenced
this issue
Sep 7, 2024
See the TODOs on what needs to be added to the VersionManager fixes #111
Techatrix
added a commit
that referenced
this issue
Sep 7, 2024
This commit replaces the initial setup with the following mechanism: 1. If the workspace contains a `.zigversion`, install the given Zig version. 2. If the workspace contains a `build.zig.zon` with a `minimum_zig_version`, install the next available Zig version. 3. Check if the "Install Zig" has been previously executed in the active workspace. If so, install that version. 3. Otherwise fallback to the latest tagged release of Zig. Some parts of this are not fully implemented. fixes #111
3 tasks
Techatrix
added a commit
that referenced
this issue
Sep 24, 2024
See the TODOs on what needs to be added to the VersionManager fixes #111
Techatrix
added a commit
that referenced
this issue
Sep 24, 2024
This commit replaces the initial setup with the following mechanism: 1. Check if the "Install Zig" has been previously executed in the active workspace. If so, install that version. 2. If the workspace contains a `.zigversion`, install the given Zig version. 3. If the workspace contains a `build.zig.zon` with a `minimum_zig_version`, install the next available Zig version. 4. Otherwise fallback to the latest tagged release of Zig. Some parts of this are not fully implemented. fixes #111
Techatrix
added a commit
that referenced
this issue
Sep 29, 2024
See the TODOs on what needs to be added to the VersionManager fixes #111
Techatrix
added a commit
that referenced
this issue
Sep 29, 2024
This commit replaces the initial setup with the following mechanism: 1. Check if the "Install Zig" has been previously executed in the active workspace. If so, install that version. 2. If the workspace contains a `.zigversion`, install the given Zig version. 3. If the workspace contains a `build.zig.zon` with a `minimum_zig_version`, install the next available Zig version. 4. Otherwise fallback to the latest tagged release of Zig. Some parts of this are not fully implemented. fixes #111
Techatrix
added a commit
that referenced
this issue
Oct 12, 2024
See the TODOs on what needs to be added to the VersionManager fixes #111
Techatrix
added a commit
that referenced
this issue
Oct 12, 2024
This commit replaces the initial setup with the following mechanism: 1. Check if the "Install Zig" has been previously executed in the active workspace. If so, install that version. 2. If the workspace contains a `.zigversion`, install the given Zig version. 3. If the workspace contains a `build.zig.zon` with a `minimum_zig_version`, install the next available Zig version. 4. Otherwise fallback to the latest tagged release of Zig. Some parts of this are not fully implemented. fixes #111
Techatrix
added a commit
that referenced
this issue
Oct 25, 2024
This commit replaces the initial setup with the following mechanism: 1. Check if the "Install Zig" has been previously executed in the active workspace. If so, install that version. 2. If the workspace contains a `.zigversion`, install the given Zig version. 3. If the workspace contains a `build.zig.zon` with a `minimum_zig_version`, install the next available Zig version. 4. Otherwise fallback to the latest tagged release of Zig. Some parts of this are not fully implemented. fixes #111
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See zigtools/zls-vscode#56 and zigtools/zls#1137
Vague idea:
Add a
${arch}-${os}subfolder hereconst installDir = vscode.Uri.joinPath(context.globalStorageUri, "zls_install");Treat
zls.pathas an override - if set user is responsible for managing the executable (could still ask to install if it fails to start or if older then set to null -> use InstallDir)Starting client: check
zls.path== null (and =="") -> use InstallDirThe text was updated successfully, but these errors were encountered: