As far as I’m aware, the main problem with decompilers is the fact that they can’t name variables and functions automaticly. But that doesn’t matter if you are just going from binary -> decompiler -> compiler -> binary
And I know there’s a lot of platform dependent code like OS APIs (such as DirectX, and WinAPI). But surely there are substitutions of the functions defined in these APIs right? I think automated porting could be performed 90% of the time and the remaining 10% could be fixed with community patches
This feels like a incredibly stupid idea after writing down but I just want to know
I think licensing may have something to do with it. A proprietary licence will typically prohibit decompilation so if you do it, you’re in violation of the licence. Whether that’s enforceable… Idunno. Often just writing a rule down will make people averse to testing it. Software under a non-proprietary licence probably comes with the source code to begin with, so there’s no need. This leaves a relatively small useful area for this technique, where people either don’t mind being in potential legal trouble (or just losing their licence to use a particular piece of software) or are interested in a specific few pieces of software that don’t offer source but allow sortof digging it out of the binary directly.