summaryrefslogtreecommitdiff
path: root/external/poppler
ModeNameSize
-rw-r--r--ExternalPackage_poppler_data.mk13073logplain
-rw-r--r--Makefile228logplain
-rw-r--r--Module_poppler.mk555logplain
-rw-r--r--README111logplain
-rw-r--r--StaticLibrary_poppler.mk6078logplain
-rw-r--r--UnpackedTarball_poppler.mk593logplain
-rw-r--r--UnpackedTarball_poppler_data.mk510logplain
-rw-r--r--poppler-config.patch.114206logplain
s something we do not want 3rd-party code to do anyway). However, some JunitTest_jurt_* define classes in those sealed packages. In the past they got away with that by using gb_JunitTest_use_jar_classset,*,jurt. Instead they now need to gb_JunitTest_use_jar_classset,*,ridl and drop the gb_JunitTest_use_jar,*,ridl. But the former only makes available the classes that are specified in ridljar/Jar_ridl.mk with gb_Jar_add_sourcefiles, not the UNOIDL entities specified via gb_Jar_add_packagedirs. But the tests need the udkapi UNOIDL entities, so introduce gb_JunitTest_add_classpath to let the tests get them explicitly. (Curiously, JunitTest_jurt_uno and JnitTest_jurt_util use gb_JunitTest_use_jar_classset,*,jurt but don't seem to acutally need it; lets leave that for a follow-up clean up.) As a follow-up clean up, relevant files could be moved from jurt/ to ridljar/. Change-Id: I836f4e7bb47fb41f1306e3f223da90dba988eb9a Co-authored-by: Stephan Bergmann <sbergman@redhat.com> Reviewed-on: https://gerrit.libreoffice.org/c/core/+/84946 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>