From bbf0023bb6865777d97cfb33043d3478c863d031 Mon Sep 17 00:00:00 2001
From: Anton Khirnov <anton@khirnov.net>
Date: Tue, 17 Jan 2012 13:38:35 +0100
Subject: [PATCH] RELEASE_NOTES: mention hiding private symbols in shared
 builds.

---
 doc/RELEASE_NOTES | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/doc/RELEASE_NOTES b/doc/RELEASE_NOTES
index 218a81b544e..8c642b9e4df 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.
-- 
GitLab