[systemd-devel] [PATCH] build: generate pkg-config files during configure

Dimitri John Ledkov dimitri.j.ledkov at intel.com
Fri Mar 13 02:39:59 PDT 2015

On 12 March 2015 at 23:13, Jeff Waugh <jdub at bethesignal.org> wrote:
> On Fri, Mar 13, 2015 at 10:07 AM, Michael Biebl <mbiebl at gmail.com> wrote:
>>> Those are the as-installed versions (they're not manipulated again during make).
>> And how does that improve cross-compilation?
> It allows you to successfully build other software that uses the
> library. A minor detail. :-)

I don't buy this.

When cross-compiling with pkg-config, you do need to ship the
pkg-config files in a different place, in the same location one sets
prefix to. and then use e.g. /usr/bin/arm-linux-gnueabihf-pkg-config
(via wrapper) or simply set PKG_CONFIG_PATH correctly.

Having done a few cross-bootstraps from scratch I don't recall any
bugs/problems with crossbuilding systemd itself, or things that depend
on libsystemd & friends. Can you start from beginning as to how you
are cross compiling things on the OpenWRT and why it is failing for
you? What is your host? What is your cross-chroot? What are your
PKG_CONFIG_PATH? What's the contents of the generated .pc file? Where
do you install it, and how does it fail for you?



Open Source Technology Center
Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.

More information about the systemd-devel mailing list