On 02/28/2012 04:38 PM, Darrell Anderson wrote:
<snip>
> I treat both Qt3 and TQt3 the same in my build scripts. In my build scripts I modify the "T" or "t" prefix as necesary but use the same environment variables during the build, such as $QTDIR. I install both to $PREFIX, which for me is /opt/trinity.
> 
> For /etc/profile.d, my TQt3 build script installs tqt3-trinity.sh rather than qt3.sh. I use the "-trinity" suffix because I also build KDE3. I do not want qt3.sh from KDE3 or Trinity overwriting each other. Thus my qt3 build script installs qt3-trinity.sh. The name of the script is less important except as a guide to the purpose. As long as the script is executable the contents executes the same.
> 
> I have my (T)Qt3 build scripts install to /opt/trinity and not to any obtuse /opt/trinity/lib/qt3-3.3.3.d directory as was the past practice in many distros. Therefore the (T)Qt3 bin files all install to /opt/trinity/bin and I don't have to create any sym links in /opt/trinity/bin to find those bin files. Likewise for all of the (T)Qt3 lib and include files --- no weird deeply embedded directories, just the normal /opt/trinity/lib and /opt/trinity/include. Much simpler.
> 
> I no longer build Qt3, only TQt3. Slowly Tim is paying less attention to Qt3 and instead focuses on TQt3. For sure tdebindings will not build at all with Qt3 but builds with TQt3.
> 
> Darrell
> 
> 

Darrell,

  Excellent. That is exactly what I needed to know. Arch has no TQt3 build
script, so I'm just cannibalizing the Qt3 build script. I'll kick off the build
in the next few minutes and see if I get the same non-fatal warnings you are seeing.


-- 
David C. Rankin, J.D.,P.E.