Guys, Gals,
When building TQt3 to replace Qt3, what is the name for the recommended install dir (i.e. $QTDIR)? I am going to put it in /opt, so should it go in:
/opt/TQt3
or should I use it as a direct replacement and put it in
/opt/Qt3?
Specifically, I am attempting this on archlinux where I have only used Qt3 before. Is this advisable, or should I just stay with Qt3?
If I install TQt3, then will updating /etc/profile.d/qt3.sh be the proper way to tell the rest of the system where to find Qt3 --or-- should I create a new profile named tqt3.sh with that information??
Guys, Gals,
When building TQt3 to replace Qt3, what is the name for the recommended install dir (i.e. $QTDIR)? I am going to put it in /opt, so should it go in:
/opt/TQt3
or should I use it as a direct replacement and put it in
/opt/Qt3?
Specifically, I am attempting this on archlinux where I have only used Qt3 before. Is this advisable, or should I just stay with Qt3?
Put TQt3 in its own directory, e.g. on Debian the tqt3 include files live in /usr/include/tqt3 while the stock qt3 include files live in /usr/include/qt3.
TQt3 allows you to build the languange bindings for Perl, Python, etc. and will allow the usage of Qt4 libraries in TDE apps. Sticking with Qt3 only is a dead end, and you will need to upgrade sooner or later (or miss out on some new TDE features).
Tim
When building TQt3 to replace Qt3, what is the name for the recommended install dir (i.e. $QTDIR)? I am going to put it in /opt, so should it go in:
/opt/TQt3
or should I use it as a direct replacement and put it in
/opt/Qt3?
Specifically, I am attempting this on archlinux where I have only used Qt3 before. Is this advisable, or should I just stay with Qt3?
If I install TQt3, then will updating /etc/profile.d/qt3.sh be the proper way to tell the rest of the system where to find Qt3 --or-- should I create a new profile named tqt3.sh with that information??
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
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.
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.
What about patches? Are the same patches applicable to Qt3 also applicable to TQt3? I built Qt3 from git with the following patches:
Unlikely. I won't pretend to understand the technical reasons, but TQt3 uses different naming schemes. After you install the TQt3 package you'll notice header files use an "nt" prefix. Look at the tqtinterface sources and notice there is a interface_qt3 and interface_tqt3 directory. Tim can correct me, but I believe any Qt3 patches have to be modified for TQt3.
One of these days --- some day --- I wish Tim would write a nice technical article for the wiki explaining the entire TQ interface layer. :)
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?
I don't use any patching with (T)Qt3. If those patches are useful then perhaps pop them into an enhancement request.
Darrell
-
Darrell Anderson -
David C. Rankin -
Timothy Pearson