Hi everyone!
El miércoles, 16 de enero de 2019 14:53:19 -03 Helmut Grohne escribió:
> Hi Chris,
>
[snip]
> > I had a chance to review the patch. The fix hinges on this function call:
> > PKG_CONFIG = $$pkgConfigExecutable()
> >
> > Could you let me know where this function call exists, i.e. what package
> > it's in so I can look at it? I haven't been able to find it, and to try
> > to get a patch upstream I need to understand and be able to explain what
> > this is for and what it does.
>
> Unfortunately, I cannot precisely answer that question. I'll have to
> defer to Lisandro or Dmitry (both Cced here). In any case, the reason is
> that your dependencies (aka .pc files) may be present for multiple
> architectures and for cross building that matters. So you need to
> somehow specify to pkg-config, which architecture you are interested in.
> On Debian systems you do that by invoking a different pkg-config.
> Typically, that's ${DEB_HOST_GNU_TYPE}-pkg-config. So I can tell, what
> this call does (but not where it comes from): It returns the pkg-config
> that the user (in this case dh_auto_configure) supplied to the build.
>
> A quick codesearch[1] reveals that it is defined somewhere in
> qtbase-opensource-src, so it should come with any qmake installation
> based on qt5.qmake as a build system has support for using pkgconfig. I have not used this myself (I strongly prefer CMake), but glazing at the code it's just the way qmake passes the path to pkgconfig. Kinds regards, Lisandro. -- "A computer is like an air conditioner. It stops working when you open windows." Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
signature.asc
Description: This is a digitally signed message part.
