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
@@ -229,7 +229,7 @@ The demo SDK integrates the [S-CORE toolchain with two extensions](https://githu
229
229
### Bazel Rules for the Example Applications
230
230
231
231
The example extends the [`scrample` example](https://github.com/eclipse-score/scrample) of S-CORE with the application setup and the toolchain extensions described above.
232
-
With those changes, the toolchain can be used via `bazel build --config=aarch64 --spawn_strategy=local //scrample_integration:<target>`.
232
+
With those changes, the toolchain can be used via `bazel build --config=aarch64-ebclfsa //scrample_integration:<target>`.
233
233
234
234
> [!IMPORTANT]
235
235
> Building inside a sandbox is currently not possible.
@@ -253,7 +253,7 @@ The following sections introduce some of the rules mentioned above.
253
253
The `run` target provides an easy entry point, to build, post-process, deploy, run and stop the example:
This will first download the image via the `fetch-fastdev-archive` rule and cache the archive.
@@ -362,7 +362,7 @@ ssh -p 2222 root@localhost
362
362
For deploying the example application to the image, the `upload` rule is available, which will start the image based on the content of `bazel-bin/scrample_integration/deb-qemuarm64/` and deploy all needed files via `scp`.
Since the deployment step will change the stored disk image, the `upload` rule stores its output in `bazel-bin/scrample_integration/deb-qemuarm64-modified/`.
0 commit comments