1
0
mirror of https://gitlab.xiph.org/xiph/ezstream.git synced 2024-11-03 04:17:18 -05:00

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
This commit is contained in:
moritz 2009-08-01 16:15:50 +00:00
parent 899cc1d393
commit 0388f0fab8

13
README
View File

@ -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 If this procedure is unfamiliar to you, please consult the INSTALL file for
more detailed instructions. 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 When the configuration keeps failing despite having all dependencies
installed, take note of the more verbose error messages in config.log. If 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 environment variables. See the "influential environment variables" list
in the --help output. in the --help output.