[Qbs] How to pass information to custom module via Depends ?
Glenn Coombs
glenn.coombs at gmail.com
Tue Feb 21 03:33:08 CET 2017
Thanks for pointing out the qbs.sysroot property. I did not have that
property set for my cross compilation toolchain. After using qbs-config to
add the property I was able to remove my code for setting the pkg-config
executable and it worked as you described, automatically adding the
necessary sysroot options.
On 15 February 2017 at 23:38, Christian Kandeler <christian.kandeler at qt.io>
wrote:
> On 02/15/2017 04:10 PM, Glenn Coombs wrote:
> > What is the procedure for creating suggestion issues on JIRA - is it okay
> > to just create one or is it best to ask questions on this list first ?
>
> If you feel you have a good understanding of the problem, then just go
> ahead and create the bug report. We can always close it if we don't
> agree, and it's a more suitable platform for discussing bugs and
> concrete features.
>
> > Specifically, I'm thinking about the way that PkgConfigProbe uses the
> PATH
> > environment to find the pkg-config executable. When cross compiling it
> > would be more convenient for it to prepend the toolchain directory to the
> > PATH so that the target version of pkg-config is used instead of the host
> > version.
>
> Why? As far as I understand, the knowledge is inside the .pc files, not
> the tool itself. And the respective environment variables
> (PKG_CONFIG_SYSROOT_DIR and PKG_CONFIG_LIBDIR) are set to suitable
> values in the presence of a sysroot, so I don't see what the issue with
> cross-compiling would be.
>
>
> Christian
> _______________________________________________
> Qbs mailing list
> Qbs at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qbs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qbs/attachments/20170221/65defa44/attachment.html>
More information about the Qbs
mailing list