Replies: 3 comments
-
I believe Bazel is doing the right thing here and building the js_binary for the target platform. For build actions that use a js_binary, those should still be built for the execution platform via the |
Beta Was this translation helpful? Give feedback.
-
My use case is, that i have a code-generator written in Javascript/ Typescript and a C/C++ Target Application, which depends on the generated sources and is compiled for the target platform. |
Beta Was this translation helpful? Give feedback.
-
Can you provide more details as to how the js_binary is being executed? Is it a custom rule? Are you calling |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What happened?
When using a custom target platform for a different os than the execution platform, the wrong launcher script is selected.
E.g. selecting a windows target platform on a linux execution platform, selects the windows launcher script and vice-versa.
Version
Development (host) and target OS/architectures:
Output of
bazel --version
:aspect 5.2.1
Version of the Aspect rules, or other relevant rules from your
WORKSPACE
orMODULE.bazel
file:0eca3b9
Language(s) and/or frameworks involved:
C/C++ and JS, TypeScript
How to reproduce
Add a custom target platform for cross compile to a different OS than windows and try to build under windows.
Any other information?
https://github.com/nosamad/rules_js/tree/topic/fix_launcher_script_selection
Beta Was this translation helpful? Give feedback.
All reactions