A build helper script can be found at dev/build.sh
.
./dev/build.sh
./dev/build.sh
powershell -ExecutionPolicy ByPass -File .\dev\build.ps1
or "C:\Program Files\Git\bin\bash.exe" ./dev/build.sh
The insider
version can be built with ./dev/build.sh -i
on the insider
branch.
You can try the latest version with the command ./dev/build.sh -il
but the patches might not be up to date.
The script dev/build.sh
provides several flags:
-i
: build the Insiders version-l
: build with latest version of Visual Studio Code-o
: skip the build step-p
: generate the packages/assets/installers-s
: do not retrieve the source code of Visual Studio Code, it won't delete the existing buildHere is the base script to build VSCodium:
# Export necessary environment variables
export SHOULD_BUILD="yes"
export SHOULD_BUILD_REH="no"
export CI_BUILD="no"
export OS_NAME="linux"
export VSCODE_ARCH="${vscode_arch}"
export VSCODE_QUALITY="stable"
export RELEASE_VERSION="${version}"
. get_repo.sh
. build.sh
To go further, you should look at how we build it:
The ./dev/build.sh
script is for development purpose and must be avoided for a packaging purpose.
# for the stable version
cd ./stores/snapcraft/stable
# for the insider version
cd ./stores/snapcraft/insider
# create the snap
snapcraft --use-lxd
# verify the snap
review-tools.snap-review --allow-classic codium*.snap
./dev/build.sh
, if a patch is failing then,./dev/update_patches.sh
Press any key when the conflict have been resolved...
, open vscode
directory in VSCodium*.rej
filesnpm run watch
./script/code.sh
until everything is okupdate_patches.sh
./dev/build.sh
, if a patch is failing then,./dev/patch.sh <name>.patch
where <name>.patch
is the failed patchvscode
directory in a new VSCodium's window*.rej
filesnpm run watch
./script/code.sh
until everything is ok./dev/patch.sh
, press enter
to validate the changes and it will update the patchTo run icons/build_icons.sh
, you will need:
npm install png2icns -g
)