Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index 

On 06/10/2015 03:35 PM, Khaled Hosny wrote:

but since we already have PATH in config_host.mk it would perhaps be
possible to detect which directory the pkg-config is found in and
automatically filter that out of $PATH (unless it's something that
cannot be removed like /usr/bin).  would that be an improvement for you,
and/or would anybody object to that?



I think setting PKG_CONFIG_* environment variables to empty values will
make pkg-config not find any installed libraries, so if we can do that
for LibreOffice build shell (or whatever it is called) on Mac OS X
(either by default or only when pkg-config is found) it should make its
presence an non concern for LibreOffice build.
I don't like any of that tweaking of env vars in the build system. It makes matters more opaque instead of more transparent.
And while presence of pkg-config on the PATH might be a good heuristic to detect that the environment has been contaminated by MacPorts or their like, is polluting PATH the only thing those do (and which we would thus need to counter), or are they also polluting in other ways that subtly influence the build (and then cause headaches)?

Context

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.