aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorAnton Khirnov <anton@khirnov.net>2012-01-17 13:38:35 +0100
committerAnton Khirnov <anton@khirnov.net>2012-01-18 14:35:53 +0100
commitbbf0023bb6865777d97cfb33043d3478c863d031 (patch)
treeaa78fb571c9934bfc0b5ff426e11204d01acd8b8 /doc
parent26f71ef48c0b6fb9f278528c8251850a76bcd3fe (diff)
downloadffmpeg-bbf0023bb6865777d97cfb33043d3478c863d031.tar.gz
RELEASE_NOTES: mention hiding private symbols in shared builds.
Diffstat (limited to 'doc')
-rw-r--r--doc/RELEASE_NOTES9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/RELEASE_NOTES b/doc/RELEASE_NOTES
index 218a81b544..8c642b9e4d 100644
--- a/doc/RELEASE_NOTES
+++ b/doc/RELEASE_NOTES
@@ -70,4 +70,13 @@ similar programmer-centric information.
Other notable changes
---------------------
+Libavcodec and libavformat built as shared libraries now hide non-public
+symbols. This will break applications using those symbols. Possible solutions
+are, in order of preference:
+1) Try finding a way of accomplishing the same with public API.
+2) If there is no corresponding public API, but you think there should be,
+post a request on the user mailing list or IRC channel.
+3) Finally if your program needs access to Libav internals for some special
+reason then the best solution is to link statically.
+
Please see the Changelog file for a more detailed list of changes.