My boss wants me to make a project developed with Qt 4.1.4 on FC5 to run on FC2. The new guy always gets the fun projects, ugh.

So I've got a licensed copy of Qt 4.1.4, ran configure, make, and make install. Qt installed to /usr/local/Trolltech/Qt-4.1.4/.

I presume I must add the bin subdirectory to the PATH, and redirect QTDIR to this new directory. Another thing I think I must do is append LD_LIBRARY_PATH. Below is part of my .bash_profile:

QTDIR=/usr/local/Trolltech/Qt-4.1.4/
export QTDIR
export $LD_LIBRARY_PATH:/usr/local/Trolltech/Qt-4.1.4/lib

So here's a brief summary of my problems:

1) cd /root/Desktop/gct && QTDIR="/usr/local/Trolltech/Qt-4.1.4/" gmake -j1
2) qt_config.prf:8: Unknown test function: debug
3) include/qteditorfactory.h:24:19: QObject: No such file or directory

In the KDevelop output window we start out with 1 (yes, I must compile the project as root due to the nature of the project, don't ask - NDA) I have no idea what 2 is all about or how to fix it. It's the first message I get after 1, and I get a bunch of them. 3 has many instances, where the Qt include files are not being found (QObject is an example).

I'm foremost a Windows developer, transitioning to a linux enviroment, so I'm in need of some help here, getting Qt 4.1.4 working on FC2. Any insight towards getting this working would be greatly appreciated.

Thanks in advance.

Really this is a bad idea all the way around, FC2 has been moved to legacy mode a while ago and now has been retired*, please see; http://www.fedoralegacy.org/


*retired is short for your on your own, everyone is not supporting is anymore, consider this to be a 'dead' OS.

Maybe your boss does not realize this???? Or this is some sort of test for you?????

I'm aware that FC2 is legacy, but in a company of 1300 employees, its not easy keeping everyone up to speed. That and there are technical reasons I cannot go into. So you cannot simply suggest a Silver Bullet fix as drastic as FC2 being a bad idea; It has little to do with assisting this issue.

But I got the solution. The big thing was learning the "env" command, and finding out I needed to place the new Qt-4.1.4 bin directory before wherever the Qt-3.3.3-7 bin directory was located in the PATH variable. That obsolved all problems.