mirror of
https://github.com/ankitects/anki.git
synced 2025-11-13 16:17:13 -05:00
docs: the old TS flakiness should be gone, but renames are a problem
This commit is contained in:
parent
c2768e2188
commit
ad2c17aced
2 changed files with 9 additions and 11 deletions
|
|
@ -203,11 +203,13 @@ Recording also requires `lame` to be in your system path.
|
||||||
If you get errors with @npm and node_modules in the message, try deleting the
|
If you get errors with @npm and node_modules in the message, try deleting the
|
||||||
node_modules folder.
|
node_modules folder.
|
||||||
|
|
||||||
Unlike the old Make system, a "clean build" should almost never be required
|
On Windows, you may run into 'could not write file' messages when TypeScript
|
||||||
unless you are debugging issues with the build system. But if you need to get
|
files are renamed, as the old build products are not being cleaned up correctly.
|
||||||
things to a fresh state, you can run `bazel clean --expunge`. After doing so,
|
You can either remove the problem folder (eg
|
||||||
make sure you remove the node_modules folder, or subsequent build commands
|
bazel-out/x64_windows-fastbuild/bin/ts/projectname), or do a full clean.
|
||||||
will fail with a "no such file or directory node_modules/anki" message.
|
|
||||||
|
To do a full clean, use a `bazel clean --expunge`, and then remove the node_modules
|
||||||
|
folder.
|
||||||
|
|
||||||
## Tracing build problems
|
## Tracing build problems
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -25,9 +25,9 @@ After installation completes, run msys2, and run the following command:
|
||||||
$ pacman -S git
|
$ pacman -S git
|
||||||
```
|
```
|
||||||
|
|
||||||
**Bazelisk**:
|
**Bazel**:
|
||||||
|
|
||||||
Use Start>Run to open PowerShell. Create a folder to store Bazelisk
|
Use Start>Run to open PowerShell. Create a folder to store Bazel
|
||||||
and its working data. Anki's build scripts expect to find it in \bazel on the same drive as the source folder.
|
and its working data. Anki's build scripts expect to find it in \bazel on the same drive as the source folder.
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
@ -61,10 +61,6 @@ This will build Anki and run it in place.
|
||||||
The first build will take a while, as it downloads and builds a bunch of
|
The first build will take a while, as it downloads and builds a bunch of
|
||||||
dependencies. When the build is complete, Anki will automatically start.
|
dependencies. When the build is complete, Anki will automatically start.
|
||||||
|
|
||||||
The Javascript build code is currently a bit flaky, so the initial
|
|
||||||
build may fail with an error. If you get an error when running/building,
|
|
||||||
try repeating the command once or twice - it should pick up where it left off.
|
|
||||||
|
|
||||||
To play and record audio, mpv.exe and lame.exe must be on the path.
|
To play and record audio, mpv.exe and lame.exe must be on the path.
|
||||||
|
|
||||||
## Optimized builds
|
## Optimized builds
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue