feat: automatically compile binary when doing `pop up network`

[Daanvdplas]

I launch a network and I see some mistake in my runtime. I fix the changes and I then want to launch the network again. I don't want to compile separately from entering the pop up command, it should do it for me so that the user can be certain it always uses the binary with the latest changes.

There should be a flag where you can specify to not compile: --no-build

Ref: https://x.com/Moliholy88/status/1905531031966335143

[chungquantin]

Hmm the issue with this is the network config file can be configured with different chains / runtimes and we don't know which binaries to rebuild. One possible solution is to prompt MultiSelect the user on binaries to rebuild (only including binaries that are specified locally). For example, default_command = "./target/release/pop-node" in pop-node/devnet

[moliholy]

@Daanvdplas I think the issue title is not correct. The X thread (of which I participated in) mentions the bench command, not the up one.

EDIT: when benchmarking the pallets, I see it already builds the project if using a directory.

[Daanvdplas]

Yeah so if I remember correctly this should also be the case for deploying a network with your custom chain, same for contract when you want to deploy it.