00:28 <petekubiak[m]> Maybe I'm misunderstanding but could you do something like this?... (full message at <https://catircservices.org/_irc/v1/media/download/ARWv6UEvrgLrj9483kZ9RM7Yf35RJe8Yq7vZqonlSSnQJT9im8qEQQenXKy2ZE0tG1JHYgYCV52tq0Qp_yHZYD-_8AAAAAAAAGNhdGlyY3NlcnZpY2VzLm9yZy9CblhYT1BIZWpyeU5PV3BDUnRUdElBT08>)

11:53 <igiona[m]> <PhilMarkgraf[m]> "Is anyone using Bazel or Buck2..." <- > <@shakencodes:matrix.org> Is anyone using Bazel or Buck2 build systems with their embedded systems work?... (full message at <https://catircservices.org/_irc/v1/media/download/ATX3g8jQV4lhLrILNeEhIKwCdObcsXiHLtFjnaZE9AEsdxEcqZ9W6gblJwlCd8UkFwRPZVec7dD76OPHuOcQH_6_8AAAAAAAAGNhdGlyY3NlcnZpY2VzLm9yZy9DV09zRWNCSmF3WUlQY0J4Wk1sbEpoZW8>)

19:17 <RockBoynton[m]> I have had to be stuck on an older rust release (1.78) for a while, but was finally able to upgrade to 1.83. What are some niceties added that I can now add to my firmware code with? For sure two I know of are error_in_core so I can use thiserror, and expecting lints.

19:47 <scorpion2185[m]1> is there a nice way to have a main menu where each entry open some state that can be another menu?

20:24 <igiona[m]> s/now/no/, s///, s///

20:38 <Mathias[m]> <igiona[m]> "> <@shakencodes:matrix.org> Is..." <- I have spoken to Steve Klabnik on the same topic. Many Embedded Rust projects use tooling in addition to Cargo: Makefile, xtask, etc. So there are opportunities for enhancements in... (full message at

20:38 <Mathias[m]> <https://catircservices.org/_irc/v1/media/download/AVzOdBSHefr2NKkigy895s9OULMPwI4dbOEgkIlExi_--naEceQOrg5gICOasEp_kb9DzKWavj6YKOgV2aKdu-W_8AAAAAAAAGNhdGlyY3NlcnZpY2VzLm9yZy9tVlRTREpUTGV3dVFjb3J0dnZwdEJNcEs>)

20:46 <dirbaio[m]> bazel/buck do sandboxing?

20:47 <dirbaio[m]> * do sandboxing to mitigate the "arbitrary code" thing?

21:34 <igiona[m]> If crates.io security is a concern, then you're looking at a completely different problem than "just" cross compilation.... (full message at <https://catircservices.org/_irc/v1/media/download/AYYwrtwZhRabaDbHxwCRsAbfLcUt46c62rkNT7QFRQZXTLBrY1AeqqZrRBf_U-fn3MNA9_afOhTOwSfyNluP1Au_8AAAAAAAAGNhdGlyY3NlcnZpY2VzLm9yZy9aZ2tTYkl6SnhRSk5EdGdkR2djcVpaeks>)

21:36 <igiona[m]> My point is: if Cargo is missing features, it would be best to enhance it rather than using bazel to solve them.

21:36 <igiona[m]> I would prefer the investment of companies going in that direction rather than finding a workaround to it

21:40 <igiona[m]> But yeah, the concerns you have listed can be real for certain companies, especially in regulated environments.

21:40 <igiona[m]> We use Yocto to integrate rust applications, so the cross compilation part of it is "solved" by Yocto itselfs (or by the Yocto nativeSDK)

21:42 <igiona[m]> <dirbaio[m]> "bazel/buck do sandboxing?" <- As far as I remember, in Bazel everything is like running in a chrooted environment where only what's specified comes in and out.

21:42 <dirbaio[m]> yeah but that's for reproducibility. it's not a security boundary to prevent you getting pwned by malicious arbitrary code

21:42 <igiona[m]> And then it learns the dependency tree from there

21:45 <igiona[m]> Mmmm true, but I guess it kind of reduces the scope of what a malicious code can access.

21:45 <igiona[m]> In build.rs you can access every part of the FS I guess? Provided you have permissions to do so of course