I'm trying to build VS Code from github on a RPi 4 running buster.
I was able to get this first command to execute successfully (albeit with warnings) from a console within the directory into which I cloned the source code:
./scripts/npm.sh install --arch=armhf
But when I fired up the launch script from within a console inside of Remote Desktop window (I'm accessing the Pi from within Windows 10):
./scripts/code.sh
the script runs correctly with the following output:
mark@sherlock:~/vscode $ ./scripts/code.sh
yarn run v1.19.1
$ node build/lib/electron
Done in 1.28s.
[16:20:35] Syncronizing built-in extensions...
[16:20:35] You can manage built-in extensions with the --builtin flag
[16:20:35] [marketplace] ms-vscode.node-debug@1.40.1 ✔︎
[16:20:35] [marketplace] ms-vscode.node-debug2@1.39.2 ✔︎
[16:20:35] [marketplace] ms-vscode.references-view@0.0.30 ✔︎
yarn run v1.19.1
$ gulp compile --max_old_space_size=4095
...but gulp compile has been running for over 90 minutes now, with top showing that CPU utilization is pegged for gulp compile at 99+%.
Is this normal? Is there a build/compile log somewhere that I can check to see what's going on?