Closed rouault closed 2 months ago
Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml
) and found it was in an excellent condition.
poppler was one of the main things that drove #722. Does poppler just need to be present at build time and not at run?
Does poppler just need to be present at build time and not at run?
just at build time. Technically it doesn't even need to be there. Just having -DHAVE_POPPLER in CXXFLAGS of libgdal-core should be enough
just at build time.
I believe adding it as a dep will cause it to be added as a run dep, unless we do some tricks. Will research this more soon and hopefully I am wrong :)
Technically it doesn't even need to be there. Just having -DHAVE_POPPLER in CXXFLAGS of libgdal-core should be enough
trying that approach in https://github.com/conda-forge/gdal-feedstock/pull/976
I believe adding it as a dep will cause it to be added as a run dep, unless we do some tricks.
I don't think so. I didn't see any run_exports
:
https://github.com/conda-forge/poppler-feedstock/blob/main/recipe/meta.yaml
Can a simple test be added to the libgdal-pdf
artifact section to ensure that it is working?
Can a simple test be added to the
libgdal-pdf
artifact section to ensure that it is working?
attempted in #976 with 41f671383fa4ab65fdf7bc4fb66faaf0bf6ede0b
closing as superseded per #976
due to poppler not being found when building libgdal-core
which causes the plugin to emit the following and not being functional: