... | ... | @@ -168,6 +168,6 @@ The safest way to bump lib version for newer development or release artifacts is |
|
|
- if the library has not changed at all, leave version info untouched
|
|
|
- if any change has been made to the library source code, bump 'current' and set 'revision' and 'age' to 0
|
|
|
|
|
|
This will guarantee that the new library needs to be recompiled in order to be used by older or newer versions of the binary.
|
|
|
This will guarantee that the new library needs to be recompiled every time with entire source tree, avoiding any bad linkage or dynamic symbol loading.
|
|
|
|
|
|
This can also be automate the process by the release procedure. |
|
|
\ No newline at end of file |