Age | Commit message (Collapse) | Author | Files | Lines |
|
337585e3d881c2c2c9099888b09902119dc05bf8 unconditionnaly
overrides any potential user-defined CMAKE_C[XX]_FLAGS.
This for example breaks the GDAL oss-fuzz builds which build Poppler
from source (see https://github.com/OSGeo/gdal/blob/master/gdal/fuzzers/build.sh#L54)
So do the same as the GCC path where we save input CMAKE_C[XX]_FLAGS
and reinject them in custom CMAKE_C{XX}_FLAGS_{build_configuration}
The values are identical to GCC, execpt for the _DEBUG configuration
where we remove '-O2 -fno-reorder-blocks -fno-schedule-insns -fno-inline'
since clang does not support -fno-reorder-blocks and -fno-schedule-insns,
so it is likely better to disable any optimization for proper debugging.
|
|
This code needs a bit of refactoring to share most of it between gcc and
clang
|
|
It's always a bad idea having multiple variables with the same name, so complain if that happens
|
|
|
|
|
|
This is nowadays also provided by CMake itself via CMakePushCheckState.
|
|
|
|
There's no reason it can't be available (either natively, or when
cross-compiling with mingw).
|
|
We only support lcms2 for a while
|
|
|
|
|
|
It wasn't working since the if mentioned LIBOPENJPEG2_INCLUDE_DIR instead of LIBOPENJPEG2_INCLUDE_DIRS
and when fixing the typo it broke the build because we were not defining USE_OPENJPEG2, so better just
remove the broken if code
|
|
And increate gdk pixbuf requirement to the version i think we actually require
|
|
|
|
Also add two enum values in the qt5 frontend to representate no flags
Also mark glib/gtk/cairo system includes so that gcc doesn't report the issues in those headers
|
|
builds fine without warnings
|
|
|
|
|
|
Make BUILDTESTS_ADDED a global property, so the `buildtests` target gets added only once. As far as I understood, this seems to fulfil the requirements of CMP0002.
Bug #103003
|
|
|
|
This allows users to set various install directories, e.g.
libdir, includedir, mandir...
Bug #103211
|
|
and make -Wundef a default warning
|
|
poppler/glib/demo/utils.c:488:20: warning: implicit declaration of function ‘localtime_r’ [-Wimplicit-function-declaration]
if (time == 0 || !localtime_r (&time, &t)) return NULL;
^~~~~~~~~~~
The c files also need the -D_DEFAULT_SOURCE feature macro to enable non standard C++11 functons.
|
|
Since we use check_cxx_source_compiles
|
|
It depends on the same files (subset) as the gir-typelibs target meaning that sometimes when doing a parallel build you'd get the two commands trying to generate the same file at once and bad things happen
|
|
... and add it to default warning set
|
|
Most of the previous warnings are now in default. Extra warnings that
should be fixed but currently result in a lot of warnings are in the
extra group.
The old no/yes/kde COMPILE_WARNINGS option has been replaced with the
boolean option EXTRA_WARN (default off) to enable the extra warnings.
|
|
|
|
poppler/goo/gfile.cc: In function ‘GBool openTempFile(GooString**, FILE**, const char*)’:
poppler/goo/gfile.cc:409:37: error: ‘mkstemp’ was not declared in this scope
fd = mkstemp((*name)->getCString());
^
poppler/goo/gfile.cc:417:39: error: ‘fdopen’ was not declared in this scope
if (fd < 0 || !(*f = fdopen(fd, mode))) {
^
poppler/goo/gfile.cc: In function ‘int Gfseek(FILE*, Goffset, int)’:
poppler/goo/gfile.cc:558:34: error: ‘fseeko’ was not declared in this scope
return fseeko(f, offset, whence);
^
poppler/goo/gfile.cc: In function ‘Goffset Gftell(FILE*)’:
poppler/goo/gfile.cc:572:18: error: ‘ftello’ was not declared in this scope
return ftello(f);
^
|
|
There's no need to not having it enabled
|
|
|
|
This reverts commit 183dbf3249e8db2398b63a749eb010bc0a89dc35.
|
|
Bug 97262
|
|
|
|
exists.
|
|
Coded with André Esser <bepandre@hotmail.com>
Bug #16770
|
|
This is helpful on a multiarch layout where the prefix is /usr/${host}
but arch-independent files should still be installed to /usr/share.
Bug 90293
|
|
With some tweaks from Albert
|
|
gtk_tree_view_set_activate_on_single_click was introduced in 3.8
|
|
|
|
We are using long long that is not defined in ansi, so forcing ansi strictness does
not make any sense. Bug #72499
|
|
|
|
Tested by Fabio
|
|
this matches what is done in the autoconf counterpart
|
|
|
|
|
|
|
|
followup of e48c22d3b70412015b9cc07a9a6ce07845274e13 also for the CMake build system,
importing the FindLCMS2.cmake from kdelibs
|
|
Conflicts:
poppler/CairoOutputDev.cc
poppler/CairoOutputDev.h
poppler/FontInfo.cc
poppler/GfxFont.cc
poppler/GfxState.cc
poppler/GlobalParams.cc
poppler/GlobalParams.h
poppler/Lexer.cc
|
|
|