Dear Albert, Albert Astals Cid wrote: >> If non-working situation is longer than 5 years, removal of >> poppler-splash.pc and poppler-cairo.pc would be the solution? >> Or, should we have some switch to build libsplash and >> libpoppler-cairo? > > I'm going to say kill them?
Oh :-) Carlos, do you have any comments? If I add another point, libpoppler-cairo (library, not package- config file) was built by autotool building system and used by a few utilities (pdftocairo) and frontend(s) (libpoppler-glib). cmake building system does not build libpoppler-cairo, so, each compilation of the utility/library using CairoOutputDev repeat the compilation of CairoOutputDev related sources by themselves. We can find the duplicated object files in the building directories, like, poppler-github$ find build-cmake_20180128 -name "*airo*" build-cmake_20180128/poppler-cairo-uninstalled.pc build-cmake_20180128/glib/CMakeFiles/poppler-glib.dir/__/poppler/CairoFontEngine.cc.o build-cmake_20180128/glib/CMakeFiles/poppler-glib.dir/__/poppler/CairoOutputDev.cc.o build-cmake_20180128/glib/CMakeFiles/poppler-glib.dir/__/poppler/CairoRescaleBox.cc.o build-cmake_20180128/utils/pdftocairo build-cmake_20180128/utils/CMakeFiles/pdftocairo.dir build-cmake_20180128/utils/CMakeFiles/pdftocairo.dir/pdftocairo.cc.o build-cmake_20180128/utils/CMakeFiles/pdftocairo.dir/pdftocairo-win32.cc.o build-cmake_20180128/utils/CMakeFiles/pdftocairo.dir/__/poppler/CairoFontEngine.cc.o build-cmake_20180128/utils/CMakeFiles/pdftocairo.dir/__/poppler/CairoOutputDev.cc.o build-cmake_20180128/utils/CMakeFiles/pdftocairo.dir/__/poppler/CairoRescaleBox.cc.o build-cmake_20180128/poppler-cairo.pc Building libpoppler-cairo by cmake and using it in libpoppler- glib and pdftocairo is not good idea? It would be useful if some utilities using CairoOutputDev would be added in future... Regards, mpsuzuki _______________________________________________ poppler mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/poppler
