> > Well here is an interesting turn of events. I added > the following to my > > ugly script function hack: > > > > pkg-config --cflags-only-I tqt > > > > The command returns no results. > > > > When directly in a terminal the command returns the > expected > > -I/usr/lib/qt3/include -I/usr/include/tqt. > > > > So perhaps the problem is right there. For whatever > reason pkg-config is > > not running from within scripts. Or is dumping the > results to the bit > > bucket. > <snip> > > Yes, that is the problem right there! > > I would dump the environemnt (via the 'env' command) in > your terminal and > from within in the build script to see what is > different. Usually this > kind of problem is caused by an incorrectly set environment > variable. Beat you to the punch. :) I might not be a crack developer, but I can troubleshoot with some of the best. ;) 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