missing x86_64-apple-darwin13-pkg-config about osxcross

[geoff-nixon]

Do you mean a dummy replacement for x86_64-apple-darwin13-pkg-config (i.e., the symlink that's installed if you build pkg-config without the --disable-host-tool flag; or a replacement for pkg-config itself?

[pisto]

well, I suppose that setting PKG_CONFIG_LIBDIR is enough to make any pkg-config unaware of host libraries and make it work with the osxcross sysroot, or not?

[pisto]

I just checked with all the other pkg-configs I have (host, mingw32/64), and they all have a single hardcoded path, and I can change that only with PKG_CONFIG_LIBDIR. So that's the only "identity" of a pkg-config, and that is what osxcross should set imo.

[geoff-nixon]

You can use PKG_CONFIG_PATH, which will accept a colon-delimited arbitrary list.

[pisto]

No, because there might be other user scripts that set PKG_CONFIG_PATH. That is what the flag is for. The toolchain base path should go in PKG_CONFIG_LIBDIR, and that too takes a colon delimited list (and it does in my three different toolchains, with "$SYSROOT/lib/pkgconfig:$SYSROOT/share/pkgconfig").

[geoff-nixon]

Interesting! I'll have to play around with that some more — the docs aren't super clear on that at all, but it seems you're quite right.

I see now there is also PKG_CONFIG_SYSROOT_DIR, but it doesn't seem to work all that well in combination with PKG_CONFIG_PATH/PKG_CONFIG_LIBDIR...

Also (not sure what your use case is) keep in mind that pkg-config isn't used near much on Darwin (not nearly as much as it should be, IMO), due two-level namespace in dynamic linkage. But since you mentioned macports, you might also want to check out how brew handles pkg-config paths/files (and dependencies in general).

[pisto]

I think that PKG_CONFIG_SYSROOT_DIR is not the right way, because it will nevertheless look int the host pkgconfig directories and then mangle the paths. I don't think this is really what to be expected (as the message in the mailing list of your link points out).
My use case is having a unified build system for a project of mine that works on native osx, mingw and linux and cross compilation environments where possible, and I'm doing that in a linux-ish way (all libs have a configure script which possibly queries pkg-config).
I just skimmed over it (I'm familiar with ruby, brew and OSX in general), but brew seems to set PKG_CONFIG_LIBDIR too.

[tpoechtrager]

Done with a8fdaa3, but a little bit different:

*-apple-darwinXX-pkg-config always returns 1 as exit code unless OSXCROSS_PKG_* is set (which is remapped to PKG_*).