GitHub/Anki
1
0
Fork 0
mirror of https://github.com/ankitects/anki.git synced 2025-09-18 14:02:21 -04:00
Code Issues Projects Releases Packages 1 Wiki Activity Actions

Mention some PowerShell specific issues (#1675)

Browse source 
* Mention Git for Windows as alternative

* Mention powershell path issue
This commit is contained in:
RumovZ 2022-02-18 10:34:44 +01:00 committed by GitHub
parent 7741475ae0
commit 5e1432ff6b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 21 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
docs/windows.md
View file

@ -28,6 +28,11 @@ After installation completes, run msys2, and run the following command:
$ pacman -S git
```
If you have native Windows apps relying on Git, e.g. the PowerShell extension
[posh-git](https://github.com/dahlbyk/posh-git), you may want to install
[Git for Windows](https://gitforwindows.org/) and put it on the path instead,
as msys Git may cause issues with them.
**Bazel**:
Use Start>Run to open PowerShell. Create a folder to store Bazel
@ -86,3 +91,19 @@ When you run a script like .\run, MSYS and bazel will automatically be added to
the path, and Bazel will be configured to output build products into
\bazel\anki. If you want to directly invoke bazel before having run any of the
.bat files in this repo, please run tools\setup-env first.
However, this will not work in PowerShell, as .bat files are executed in a subprocess.
To invoke bazel scripts, you will have to adjust your session path manually.
One option is to create a script that sets up your Anki develop environment for you.
Here is an example:
```powershell
# put bazel and msys on path
$env:PATH = "c:\bazel;c:\msys64\usr\bin;$env:PATH"
# change working directory to anki root
Set-Location C:\code\anki
# open VSC
code .
# open powershell 7
pwsh
```