summaryrefslogtreecommitdiff
path: root/cairo/ExternalProject_cairo.mk
AgeCommit message (Collapse)Author
2013-10-17fdo#70393: move cairo to a subdir of externalKhaled Hosny
Change-Id: I5a5d43521d3d7227dadd05525e2c69c63a3f1c1b Reviewed-on: https://gerrit.libreoffice.org/6284 Reviewed-by: Björn Michaelsen <bjoern.michaelsen@canonical.com> Tested-by: Björn Michaelsen <bjoern.michaelsen@canonical.com>
2013-09-22find lots of external static libraries in UnpackedTarball dirMichael Stahl
Note: do NOT put file paths to static libraries into FOO_LIBS variables that are passed to bundled externals that are built with --enable-static: on Mac OS X this will result in .a archives that contain other .a archives as entries, and trying to link those results in errors like: ld: warning: ignoring file .../libodfgen-0.0.a, file was built for archive which is not the architecture being linked (i386) Change-Id: If2c5a458058e4da76f80b3643e55b489d1edee24
2013-08-15fdo#65244: cairo configure fails to detect libpng...Michael Stahl
... unless there is _some_ libpng.pc on the system due to the weird way it uses pkg-config. Work around that by setting an png_REQUIRES variable, which lets it use the supplied png_CFLAGS and png_LIBS. Change-Id: I3ec4b96551e3ce624748c05fe3ab9727b191ea78
2013-05-08zlib: remove ExternalPackage_zlibMichael Stahl
Change-Id: I5bce88b2044279a6563fd68c35f9c1ac824c8850
2013-05-08libpng: remove ExternalPackage_libpngMichael Stahl
Change-Id: I478a057c07b9fe850401b96297a14d7842c0703f
2013-05-07gbuild: ExternalProject: remove second parameter again...Michael Stahl
... now that everything is consistent. Change-Id: I96c15159648815554280202eb1b6d274ead4e7b8
2013-05-07gbuild: remove gb_ExternalProject_use_unpackedMichael Stahl
It must always be used exactly once, so replace it with constructor parameter. Change-Id: Ifbe87065c19a5185a5705dc461656179002ece5d
2013-02-28Resolves: fdo#61571 cairo not linking against internal libpngCaolán McNamara
the flag is called SYSTEM_LIBPNG not SYSTEM_PNG Change-Id: I703a669f544e539f7fcfa64c0121a73f0608aecc
2013-02-22quiet external module build log unless failureNorbert Thiebaud
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>
2012-11-20cairo: to actually use the right cairo-version.h...Michael Stahl
...it is necessary to overwrite dummy src/cairo-version.h because that is included with "" from src/cairo.h which means that at least GCC 4.7 looks in the current directory src/ first... Change-Id: I4a254021ad318ffb428242443f7e1e29c876915c
2012-11-20cairo: convert to gbuildMatúš Kukan
Change-Id: I1f3dd368a0d0b78b73df3baad214a1079bbbd1d3 Reviewed-on: https://gerrit.libreoffice.org/1144 Reviewed-by: Andras Timar <atimar@suse.com> Tested-by: Andras Timar <atimar@suse.com>