This can be used for both GameModel and ToolModel.
It can look something like this:
struct Executable {
path: PathBuf,
args: Vec<String>,
}I'm thinking that GameModel should have a Vec<Executable>, because a game doesn't necessarily have just one executable (i.e. launcher, DX12 vs. Vulkan version). Then we'll probably want to have some way of marking which is the primary one.
This can be used for both
GameModelandToolModel.It can look something like this:
I'm thinking that
GameModelshould have aVec<Executable>, because a game doesn't necessarily have just one executable (i.e. launcher, DX12 vs. Vulkan version). Then we'll probably want to have some way of marking which is the primary one.