95dbf30fb9
All platforms: - rename scripts/ to tools/: Bazelisk expects to find its wrapper script (used by the Mac changes below) in tools/. Rather than have a separate scripts/ and tools/, it's simpler to just move everything into tools/. - wheel outputs and binary bundles now go into .bazel/out/dist. While not technically Bazel build products, doing it this way ensures they get cleaned up when 'bazel clean' is run, and it keeps them out of the source folder. - update to the latest Bazel Windows changes: - bazel.bat has been removed, and tools\setup-env.bat has been added. Other scripts like .\run.bat will automatically call it to set up the environment. - because Bazel is now on the path, you can 'bazel test ...' from any folder, instead of having to do \anki\bazel. - the bat files can handle being called from any working directory, so things like running "\anki\tools\python" from c:\ will work. - build installer as part of bundling process Mac changes: - `arch -arch x86_64 bazel ...` will now automatically use a different build root, so that it is cheap to switch back and forth between archs on a new Mac. - tools/run-qt* will now automatically use Rosetta - disable jemalloc in Mac x86 build for now, as it won't build under Rosetta (perhaps due to its build scripts using $host_cpu instead of $target_cpu) - create app bundle as part of bundling process Linux changes: - remove arm64 orjson workaround in Linux bundle, as without a readily-available, relatively distro-agonstic PyQt/Qt build we can use, the arm64 Linux bundle is of very limited usefulness. - update Docker files for release build - include fcitx5 in both the qt5 and qt6 bundles - create tarballs as part of the bundling process
17 lines
499 B
Batchfile
17 lines
499 B
Batchfile
@echo off
|
|
pushd "%~dp0"\..
|
|
|
|
REM add msys/bazel to path if they're not already on it
|
|
where /q bazel || (
|
|
set PATH=c:\msys64\usr\bin;c:\bazel;%PATH%
|
|
)
|
|
|
|
if not exist windows.bazelrc (
|
|
rem By default, Bazel will place build files in c:\users\<user>\_bazel_<user>, and this
|
|
rem can lead to build failures when the path names grow too long. So on Windows, the
|
|
rem default storage location is \bazel\anki instead.
|
|
echo startup --output_user_root=\\bazel\\anki > windows.bazelrc
|
|
)
|
|
|
|
popd
|