Update with up-transport-vsomeip-rust build changes

[PLeVasseur]

No description provided.

[dmacattack]

do the READMEs need updating ?

[PLeVasseur]

do the READMEs need updating ?

Probably 🧐

[PLeVasseur]

Hey @ValMobBIllich -- can you take a look? As you were saying, if we get this merged and you rebase on it, then it's likely that #61 builds.

[BenediktIllich]

I feel like the env setup would possibly be more compact as a xtask program but I havent looked into those in a while... hard to read through that much bash for me :)

The fundamental change is just that the location of the cpp compiler is now dynamically determined which I guess is more stable?

[PLeVasseur]

The fundamental change is just that the location of the cpp compiler is now dynamically determined which I guess is more stable?

Exactly, it will be automatically determined for you by running envsetup.sh. It's already "proven in use" over in up-transport-vsomeip-rust with the same over there.

I feel like the env setup would possibly be more compact as a xtask program but I havent looked into those in a while... hard to read through that much bash for me :)

Yeah, possibly! I'm open to submissions for the like in a follow-up.

[dmacattack]

Yeah, possibly! I'm open to submissions for the like in a follow-up.

Ditto. Envsetup idea stems from build systems like buildroot, yocto, openWRT, etc. bash is pretty much guaranteed to exist on the runner than anything else, and adds flexibility if the project isn't rust.

[dmacattack]

Looks good