Hi Helmut! On Wed, May 23, 2018 at 08:23:53PM +0200, Helmut Grohne wrote: > Thiago Macieira suggested an alternative approach to solving this. > Rather than telling qmake to use the "right" pkg-config at runtime, we > can tell it at build time. > > To that end we should build qtbase with a triplet-prefixed pkg-config. > > That actually works fairly well as the Debian packaging of pkg-config > ensures that <nativetriplet>-pkg-config is a symlink to pkg-config. So > just using the triplet-prefixed pkg-config always works (native and > cross). Where should we reassign this bug to? > > I think Thiago's approach is strictly better than mine, because it > ensures that qmake will always use the right pkg-config even without > passing PKG_CONFIG or PKG_CONFIG_EXECUTABLE to qmake. That should be > useful to people cross building with qmake without our cross wrapper. I wonder how this approach will work. Our triplet-prefixed qmake is a wrapper that calls the native qmake with some arguments. If we configure qmake with prefixed pkg-config path, then the native qmake will call pkg-config corresponding to *its* (native) architecture, not the architecture we are building for. What am I missing here? -- Dmitry Shachnev
Attachment:
signature.asc
Description: PGP signature