Referencing/Opening one binary in another binary

[Sze]

@Jan200101

I’ve thought about using Step.Compile.getEmittedBin in the build system but that would then reference the cache artifact and not wherever it is installed at the end.

Have you tried using this:

Removal of getInstallPath

That’s incorrect, it is specifically designed for system installs. There is literally a --system flag for this. The main issue is that the install path should not be observed in the configure phase. You can construct a LazyPath based on the install path instead which will avoid re-running the configure phase when the user changes install path. Check out std.Build.Graph.path

I think you could create the install-lazy-path with that and then use std.Build.addRunFile to create the run-step to run it?

Haven’t updated yet so I am unsure it would work, but seems theoretically possible.