Quote:
Originally Posted by snipenekkid
reasonable for use but I would say it's not as trivial as implied. If it was it would be done. Also what happens when a statically linked library that included in the compiled/tokenized app no longer function due to some change in the original branch/distro of that version of Linux?
And I think that is one of the primary points I was trying to make. It's a moving target. Add to that if some of the code used in the main app can even be ported to Linux or a given mobile device all due to those copyrights (aka license agreements) which dictate when and where the licensed code can be run.
|
As a developer, I've never experienced any issues legally speaking with porting code to Linux. Also, when it comes to statically linked code, there isn't too much of any issue with it no longer being able to be run. I still have and can run apps with static links from 10+ years back.
The reason it isn't done often, is because if there is a bug fix for any of the libraries used, you'll have to recompile the whole app to take advantage of them, and it can create binaries that are much bigger than dynamically linked ones.