#7 cross compilation painful

[Anonymous]

OK, pkg-config is an improvement over the older
*-config scripts.

However, it doesn't deal well with cross compilation,
and neither does the scripts that use pkg-config, they
all seem to pick up the tool from /usr/bin or
/usr/local/bin. When you're doing builds for 20odd
platforms, with out of sync libs, this can get a little
hairy.

In our case, we build systems that can natively and
cross compile. Ideally, one database would serve both
(so you could natively compile something, and then
cross-compile against it)

One solution is to add an environment variable,
called PKG_CONFIG_OUTPUT_PREFIX, which in conjunction
with PKG_CONFIG_PATH, makes it possible to have one
pkg_config binary on the system. Or be able to override
the default prefix with --prefix, which any well
structured .pc file would use intellegently... Another
is to keep architecture specific information in the
data files, separated by some sort of tag.

Anyway, I gotta do something along these lines and I
was wondering which way you'd have me go.

[Martijn van Beers]

Logged In: YES
user_id=1366

I'm not sure I understand what you want to do. Could
we continue this on the mailing list?
pkgconfig-devel@lists.sf.net