This website requires JavaScript.
Explore
Help
Sign In
admin
/
ci-emsdk
Watch
1
Star
0
Fork
0
You've already forked ci-emsdk
Code
Issues
Pull Requests
Actions
Packages
Projects
Releases
Wiki
Activity
Files
c69d433d8509c5c64564c2f0d054bf102a5cf67e
ci-emsdk
/
bazel
/
emscripten_toolchain
/
emcc.bat
6 lines
61 B
Batchfile
Raw
Normal View
History
Unescape
Escape
Bazel Windows Support (#929)
2021-12-20 11:24:56 -08:00
@
ECHO
OFF
Bazel: Migrate to bzlmod (#1530) This migrates the bazel integration to the new Bazel dependency system "bzlmod". bzlmod is becoming mandatory this year (see second sentence here: https://bazel.build/external/migration). This is a backwards incompatible migration, directly removing the old WORKSPACE based approach. Users will have to change how they depend on bzlmod, however I assume pretty much every user will be happy about it, because they are forced to use bzlmod anyway or add extra flags to continue to build with newer Bazel versions. Given that users normally depend on specific git commits in the old system, they won't be hit with this until they decide to upgrade emsdk. The basic principle here is simple: I took everything that WORKSPACE did and searched an alternative in bzlmod. Some interesting bits: - We have less worries about multiple versions and people depending on emscripten multiple times in different ways. This is resolved by the new system: Bazel first iterates through the MODULE.bazel files recursively, then finds the minimum version needed for each module and then executes the module extensions that define repos exactly once at that version. So no more ifs needed to detect multiple inclusions. - A bunch of nodejs stuff moves to MODULE.bazel, because that is how the nodejs module works now. As their module extension gets executed only once you need to declare everything that you could need before that in the MODULE.bazel file. A side effect of that is that we have to make a fake repository when emscripten doesn't have an arm64 binary for linux, because we can't actually figure that out in MODULE.bazel, so we have to declare that it always exists and then create one in all cases. There is a bunch of autoformatter changes in here as well, I could try to revert them if you prefer. Closes #1509
2025-04-09 23:38:12 +02:00
call
%~dp0
\env.bat
Bazel Windows Support (#929)
2021-12-20 11:24:56 -08:00
py -3
%EMSCRIPTEN%
\emcc.py
%*
Reference in New Issue
Copy Permalink