Module: libav Branch: master Commit: bbf0023bb6865777d97cfb33043d3478c863d031
Author: Anton Khirnov <[email protected]> Committer: Anton Khirnov <[email protected]> Date: Tue Jan 17 13:38:35 2012 +0100 RELEASE_NOTES: mention hiding private symbols in shared builds. --- doc/RELEASE_NOTES | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/doc/RELEASE_NOTES b/doc/RELEASE_NOTES index 218a81b..8c642b9 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. _______________________________________________ libav-commits mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-commits
