mirror of
https://github.com/github/codeql.git
synced 2025-12-16 16:53:25 +01:00
f9bc97b2a1
This should allow us to build our python and ruby code independently - in particular, we can now do shallow checkouts of one without the other. Previously, the modext introduced cross-dependency. This also reduces the amount of work we do in the crate universe processing for the other language, even though it's unused. This does need renaming the module, as otherwise the generated paths from rules_rust get too long for Windows :(
30 lines
1.2 KiB
Plaintext
30 lines
1.2 KiB
Plaintext
common --enable_platform_specific_config
|
|
common --enable_bzlmod
|
|
# because we use --override_module with `%workspace%`, the lock file is not stable
|
|
common --lockfile_mode=off
|
|
|
|
# when building from this repository in isolation, the internal repository will not be found at ..
|
|
# where `MODULE.bazel` looks for it. The following will get us past the module loading phase, so
|
|
# that we can build things that do not rely on that
|
|
common --override_module=semmle_code=%workspace%/misc/bazel/semmle_code_stub
|
|
|
|
build --repo_env=CC=clang --repo_env=CXX=clang++
|
|
|
|
# we use transitions that break builds of `...`, so for `test` to work with that we need the following
|
|
test --build_tests_only
|
|
|
|
# this requires developer mode, but is required to have pack installer functioning
|
|
startup --windows_enable_symlinks
|
|
common --enable_runfiles
|
|
|
|
# with the above, we can avoid building python zips which is the default on windows as that's expensive
|
|
build --nobuild_python_zip
|
|
|
|
common --registry=file:///%workspace%/misc/bazel/registry
|
|
common --registry=https://bcr.bazel.build
|
|
|
|
common --@rules_dotnet//dotnet/settings:strict_deps=false
|
|
common --experimental_isolated_extension_usages
|
|
|
|
try-import %workspace%/local.bazelrc
|