Generating deployed bytecode

[kaber2]

With geth supporting code overrides in many RPC calls, I would very much like to use them during development as it is much easier for me to test on a life network than dealing with any of the Solidity development frameworks. However, despite multiple attempts, so far I haven't been able to find a way to have solidity generate the deployed bytecode, i.e. the bytecode as it would look on-chain after copying, replacing immutables, running all constructors etc.

Did I overlook something or is this not possible with Solidity at the moment? Are there any other methods people use to generate bytecode for overloading in RPC calls?

[kuzdogan]

@kaber2 are you aware of the deployedBytecode output of the compiler? That is the runtime bytecode of the contract ie. the code stored at the contract address.

However it's before running the constructor, replacing immutables etc. as you mention so I'm guessing you are aware of this.

By definition the compiler can't do that because it just compiles the code into bytecode and hands it over to EVM. You can either do the "transformations" yourself (see some of them here) or you can hand the creation bytecode (bytecode in compiler output) to EVM of your choice with the appended constructor arguments and check the output which will be the final runtime bytecode.