What is the difference between binary and source compatibility conceptually ?
compilation, google-chrome, webkit
Solution
(This answer doesn't talk about the specific context of WebKit - it's not clear what exactly you mean by the various "it says" parts. I've tried to give a more general answer.)
Suppose we have a library called LibFoo, and you have built an application called SuperBar which uses LibFoo v1.
Now LibFoo v1.1 comes out.
- If this is binary compatible, then you should be able to just drop in the new binary, and SuperBar will work using the new code without any other changes
- If this is only source compatible then you need to rebuild SuperBar against v1.1 before you'll be able to use it
Problem
In the context of webkit in chromium source code ,it says it is source compatible but not binary compatible. Does it suggest that we build .dll file of webkit and build it with chrome binary ?