> Beat you to the punch. :)
>
> I might not be a crack developer, but I can troubleshoot with some of the
> best. ;)

I know. :-)

> You might not believe the cause of this entire problem. Are you ready for
> this?
>
> Setting the $CPLUS_INCLUDE_PATH in the build environment prevents
> pkg-config from running properly. The moment I commented out that export
> command in my master script, the TQT_INCLUDE_DIRS internal variable began
> populating automatically.
>
> Okay, for the record: Woo-hoo!
>
> Now, why does the $CPLUS_INCLUDE_PATH environment variable, or the
> contents thereof, affect how pkg-config runs?
>
> Second, should I be setting that environment variable?
>
> Here is my normal setting for that variable:
>
> CPLUS_INCLUDE_PATH: /usr/include/tqt:/usr/lib/qt3/include:/usr/include
>
> Those locations are legitimate.
>
> I set $CMAKE_INCLUDE_PATH to the same, but I did not start setting that
> variable until recently. That is, this TQT_INCLUDE_DIRS problem existed
> long before I started setting the $CMAKE_INCLUDE_PATH variable. The
> $CPLUS_INCLUDE_PATH is the cause.
>
> Ideas?
>
> Darrell

Don't set CPLUS_INCLUDE_PATH?

Seriously, I'm not sure why you set that variable.  I never heard of it
before, and usually the safest way to get includes added to the compiler
flags is via CXXFLAGS and CFLAGS.

If you have a specific reason for setting CPLUS_INCLUDE_PATH then that is
different.

Tim