You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
add compile_data attr to cargo_build_script (#2203)
No functional changes intended.
Before
3e124fb
this was implicitly handled by passing **binary_kwargs to the
rust_binary, now we're making this explicit.
Compile and execute a rust build script to generate build attributes
@@ -144,6 +144,7 @@ The `hello_lib` target will be build with the flags and the environment variable
144
144
| <aid="cargo_build_script-proc_macro_deps"></a>proc_macro_deps | List of rust_proc_macro targets used to build the script. |`[]`|
145
145
| <aid="cargo_build_script-build_script_env"></a>build_script_env | Environment variables for build scripts. |`{}`|
146
146
| <aid="cargo_build_script-data"></a>data | Files needed by the build script. |`[]`|
147
+
| <aid="cargo_build_script-compile_data"></a>compile_data | Files needed for the compilation of the build script. |`[]`|
147
148
| <aid="cargo_build_script-tools"></a>tools | Tools (executables) needed by the build script. |`[]`|
148
149
| <aid="cargo_build_script-links"></a>links | Name of the native library this crate links against. |`None`|
149
150
| <aid="cargo_build_script-rundir"></a>rundir | A directory to <code>cd</code> to before the cargo_build_script is run. This should be a path relative to the exec root.<br><br>The default behaviour (and the behaviour if rundir is set to the empty string) is to change to the relative path corresponding to the cargo manifest directory, which replicates the normal behaviour of cargo so it is easy to write compatible build scripts.<br><br>If set to <code>.</code>, the cargo build script will run in the exec root. |`None`|
Compile and execute a rust build script to generate build attributes
@@ -1625,6 +1625,7 @@ The `hello_lib` target will be build with the flags and the environment variable
1625
1625
| <aid="cargo_build_script-proc_macro_deps"></a>proc_macro_deps | List of rust_proc_macro targets used to build the script. |`[]`|
1626
1626
| <aid="cargo_build_script-build_script_env"></a>build_script_env | Environment variables for build scripts. |`{}`|
1627
1627
| <aid="cargo_build_script-data"></a>data | Files needed by the build script. |`[]`|
1628
+
| <aid="cargo_build_script-compile_data"></a>compile_data | Files needed for the compilation of the build script. |`[]`|
1628
1629
| <aid="cargo_build_script-tools"></a>tools | Tools (executables) needed by the build script. |`[]`|
1629
1630
| <aid="cargo_build_script-links"></a>links | Name of the native library this crate links against. |`None`|
1630
1631
| <aid="cargo_build_script-rundir"></a>rundir | A directory to <code>cd</code> to before the cargo_build_script is run. This should be a path relative to the exec root.<br><br>The default behaviour (and the behaviour if rundir is set to the empty string) is to change to the relative path corresponding to the cargo manifest directory, which replicates the normal behaviour of cargo so it is easy to write compatible build scripts.<br><br>If set to <code>.</code>, the cargo build script will run in the exec root. |`None`|
0 commit comments