On Oct 3, 2013, at 2:30 PM, Jørgen Lind <[email protected]> wrote: >> > > But if you happen to have pkg-config in your path, why should we then > not use it. The user has "one way or the other" added it to the path, > so why shouldn't it be used. > > I think the interesting question is why configure fails when you have > a version of xcb that is missing some headers. Maybe a warning would > be enough?
You may not know you have pkg-config - it got installed as a dependency of something else. I think having various utilities installed via Macports or Homebrew is quite common, but that does not mean you neccesarily want your Mac (or iOS) apps to use those libraries. I've seen the same thing happen with ICU: Qt pulls in the Macports version and then fails to compile against it. We could fix all cases one by one but that could turn out to be a long journey. Instead, let's make the default OS X build only use public API from the official SDKs. That way we get a minimal deployment that can be deployed to the app stores. If you want to use pkg-config you can then either use a different mkspec (for example when cross-compiling), or pass "-pkg-config" to configure line. Morten _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
