ed26c01be1
ExternalProject usually involve a configure and a make step that produce a bunch of output usually irrelevant including a large number of warning and other mess. now that everything is pretty much in tail_build these output get interleaved with useful output from the build of the product and actually drown them in a logorrhea of messy noise. This store the output of external modules in a log file and only print them as a whole if the module failed do build. on a non-verbose build. Change-Id: I3abfcccd6d16821a9e061a71e031b427cc283647 Reviewed-on: https://gerrit.libreoffice.org/2304 Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com> Tested-by: Norbert Thiebaud <nthiebaud@gmail.com> |
||
|---|---|---|
| .. | ||
| prj | ||
| ExternalPackage_langtag.mk | ||
| ExternalPackage_langtag_data.mk | ||
| ExternalProject_langtag.mk | ||
| liblangtag-0.4.0-configure-atomic-cflag-pollution.patch | ||
| liblangtag-0.4.0-cross.patch | ||
| liblangtag-0.4.0-mac.patch | ||
| liblangtag-0.4.0-mingw.patch | ||
| liblangtag-0.4.0-msc-configure.patch | ||
| liblangtag-0.4.0-msvc-warning.patch | ||
| liblangtag-0.4.0-msvcprojects.patch | ||
| liblangtag-0.4.0-ppc.patch | ||
| liblangtag-0.4.0-reg2xml-encoding-problem.patch | ||
| liblangtag-0.4.0-vsnprintf.patch | ||
| liblangtag-0.4.0-windows.patch | ||
| liblangtag-0.4.0-windows2.patch | ||
| liblangtag-0.4.0-xmlDocCopyNode.patch | ||
| Makefile | ||
| Module_liblangtag.mk | ||
| README | ||
| UnpackedTarball_langtag.mk | ||
| Zip_liblangtag_data.mk | ||
From [http://tagoh.bitbucket.org/liblangtag/]. An interface for BCP47 language tags. Note that (as far a I recall) liblangtag is the only "bundled" (3rd-party) library we have that we configure and build also for MSVC using an autotools+libtool based mechanism. That is rather fragile and works maybe mostly by accident. So be careful not to break it.