Hi Jussi, On 26 May 2017 at 14:55, Jussi Kukkonen <jussi.kukko...@intel.com> wrote: > On 26 May 2017 at 14:32, Emil Velikov <emil.l.veli...@gmail.com> wrote: >> b) with a wrapper script - see [1]. >> I think that the "export PKG_CONFIG_DIR=" is a typo (should be ..PATH >> instead) and is not strictly required - feel free to check either way. >> Note that the exec at the end might need to be amended to >> /path/to/$(CHOST)-pkg-config. > > We don't provide a target wrapper -- I believe because it provides no value > at all on top of the setup we have (the pkg-config that autotools finds has > all the environment variables set correctly. It is essentially > $(CHOST)-pkg-config already). > > If I've missed something, I'd be happy to hear that. At the moment I think > pkg-config just does not help in this case.
Thinking out loud, how about searching for a separate pkg-config file (wayland-scanner-native.pc as a strawman) first, then falling back to wayland-scanner.pc? The BitBake recipes could then install that somewhere in $PKG_CONFIG_PATH as a special case in the install target. Cheers, Daniel _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
