I can't tell if that's really meant to be a question, but this rules out mobile and I wouldn't attempt to sell a product on any platform that has to be rebuilt by the end user.
The rebuilding is not a compulsion, but rather a required option. You're only ruling it out if that option is impossible (which is definitely not the case on Android).
I don't really understand. The immense majority of your customers will never look at the build procedures, just like almost no one looks at the Linux kernel sources & build instructions that you can get from Sony from your smart tv. It's not like it makes the software harder to use for anyone.
How are they going to rebuild the software without looking at build procedures (in environments where dynamic linking isn't available)?
And even in an environment where dynamic linking is available, something like the Qt runtime is not comparable to the OS itself, which is obviously already installed on all target systems. It's another component that must be installed for the software to work, and as far as I know you're not allowed to distribute it willy-nilly.
I don't understand, if someone wants to build the software of course they would look at a build procedure just like I look at a recipe when I want to cook. But that will be the 0.001% of your users who want to do this. Just like if I buy a moddable car I don't expect mods to happen by magic on their own, I know that there'll be some elbow grease involved, and I'm still making this tradeoff because moddability is more important to me.
