summaryrefslogtreecommitdiffstats
path: root/scripts/libass-config
Commit message (Collapse)AuthorAgeFilesLines
* enable harfbuzz support for libassKevin Mitchell2014-02-221-1/+1
|
* libass: fix compilation with newer git versionswm42014-01-281-0/+3
|
* Disable building fribidi for nowwm42013-07-151-1/+1
| | | | | | | It completely breaks parallel builds. I couldn't find out how to get "make" not to build fribidi with parallel build enabled.
* libass-config: override FRIBIDI_CFLAGSTuncer Ayaz2013-07-061-1/+1
| | | | | | | libass/configure sets FRIBIDI_CFLAGS to "-I$(pwd)/build_libs/include/fribidi" instead of "-I$(pwd)/build_libs/include". As a workaround override FRIBIDI_CFLAGS in scripts/libass-config.
* Add support for building fribidi locallyTuncer Ayaz2013-07-061-1/+1
|
* Fix compilation on systems where autoconf will use lib64 instead of libwm42012-10-231-1/+1
| | | | | | | | | | | At least on openSUSE 12.2 x86_64, autoconf will install libass' library files into build_libs/lib64. Since we set PKG_CONFIG_PATH to build_libs/lib/pkgconfig, mpv compilation won't find the libass.pc file. Even worse, if libass is globally installed too, mpv will still use the local libass headers in build_libs/include, while linking with the globally installed libass. Fix by forcing autoconf always to use build_libs/lib.
* Initial commitwm42012-10-131-0/+8
This is based on mplayer-git [1], except that it doesn't need Python. Some features, such as specifying custom options, are not available, but these should be considered out of the scope of the basic build wrapper. [1] http://repo.or.cz/w/mplayer-build.git