On 02/28/2012 04:58 PM, David C. Rankin wrote:
> 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.
>> 

Darrell,

  What about patches? Are the same patches applicable to Qt3 also applicable to
TQt3? I built Qt3 from git with the following patches:

000-qiconview-finditem.patch
001-qiconview-rebuildcontainer.patch
002-qiconview-ctrl_rubber.patch
003-designer-deletetabs.patch
004-qvaluelist-streaming-operator.patch
005-qprogressbar-optimization.patch
006-qiconview-no-useless-scrollbar.patch
007-qiconview-rubber_on_move.patch
008-argb-visual-hack.patch
009-fix-xinput-clash.patch
010-buffered-iconview.patch
011-qlistbox-eyecandy.patch
013-print-CJK.patch
016-gcc4.patch
gcc46-arch.patch
qt-unixodbc.patch

  Looking at http://git.trinitydesktop.org/cgit/tqt3/log/ it doesn't look like
there would be any commits that would supersede the patches, but I'm not
familiar enough about it to know. Guesses?

  Also, looking at the log, it looks like TQt3 is updated from the Qt3 source
with Tim's "Automated update from Qt3" magic. If this is the case -- it's smart
and should be kept this way as long as Automated update is possible. Neat trick.

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