From 0388f0fab8cca2386f873a83f36520e473fea22f Mon Sep 17 00:00:00 2001 From: moritz Date: Sat, 1 Aug 2009 16:15:50 +0000 Subject: [PATCH] Almost everyone chooses the pkg-config(1) way and installs shout.pc. Document how to configure ezstream on differently enabled systems. ... heh, PC talk is so deliciously nasty. git-svn-id: https://svn.xiph.org/trunk/ezstream@16381 0101bb08-14d6-0310-b084-bc0e0c8e3800 --- README | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/README b/README index 5fa72c2..cb69d09 100644 --- a/README +++ b/README @@ -104,9 +104,20 @@ The compilation and installation process then boils down to the usual If this procedure is unfamiliar to you, please consult the INSTALL file for more detailed instructions. +On systems where the libshout installation does not include the required +shout.pc file for pkg-config(1), the non-standard ``shout-config'' utility +is available. However, the ezstream build system does not support the latter. + +If this is an issue, configure ezstream with + + $ ./configure \ + LIBSHOUT_CPPFLAGS="$(shout-config --cppflags)" \ + LIBSHOUT_CFLAGS="$(shout-config --cflags-only)" \ + LIBSHOUT_LIBS="$(shout-config --libs)" + When the configuration keeps failing despite having all dependencies installed, take note of the more verbose error messages in config.log. If -necessary, it is possible to directly customize many build flags through +necessary, it is possible to further customize many build flags through environment variables. See the "influential environment variables" list in the --help output.