Hello,
tqtinterface build system was massively reworked.
Available options:
QT_VERSION=3 or USE_QT3 - activate Qt3 support
--------------------
QT_VERSION=4 or USE_QT4 - activate Qt4 support
--------------------
QT_PREFIX_DIR - the place where qt is installed default: /usr For Qt3, QT_VERSION inherits QTDIR, _if_ QTDIR environment variable is set.
--------------------
QT_INCLUDE_DIR - the place where qt headers are installed default: ${QT_PREFIX_DIR}/include/qt${QT_VERSION}
--------------------
QT_LIBRARY_DIR - the place of qt libraries default: ${QT_PREFIX_DIR}/lib${LIB_SUFFIX} For Qt4, libQtGui.so presence is checked, if is not exists in ${QT_PREFIX_DIR}/lib${LIB_SUFFIX}, ${QT_PREFIX_DIR}/lib${LIB_SUFFIX}/qt4 is checked as well
--------------------
QT_LIBRARIES - list of qt libraries required for linking Default for Qt3 - qt-mt Default for Qt4 - QtCore QtGui
--------------------
QT_BINARY_DIR - the place where qt tools are installed (moc and uic) default: ${QT_PREFIX_DIR}/bin
--------------------
MOC_EXECUTABLE - absolute path to moc default: ${QT_BINARY_DIR}/moc
--------------------
UIC_EXECUTABLE - absolute path to uic default: ${QT_BINARY_DIR}/uic
--------------------
Note: PKGCONFIG_INSTALL_DIR is defaulted to /usr/lib${LIB_SUFFIX}/pkgconfig, to avoid tqt detection problems.
Note: these options are available only for tqtinterface, the rest of packages inherits it automatically from tqt (for example, you do not need to pass argument QT_VERSION=3 to kdelibs' cmake).
Okay, so what does all of this mean to me as 1) a packager and 2) an end-user? Nothing on the wiki yet. (I'll update the wiki but I haven't a clue what to write.)
Are we supposed to start building Trinity using QT4 rather than QT3?
Do we build for both QT3 and QT4 and whichever QT package the end-user has installed is the one Trinity will use?
If both QT3 and QT4 is installed which gets used by Trinity when the end-user runs Trinity?
Darrell
--- On Sun, 3/27/11, Serghei Amelian serghei@thel.ro wrote:
From: Serghei Amelian serghei@thel.ro Subject: [trinity-devel] tqtinterface build system To: trinity-devel@lists.pearsoncomputing.net Date: Sunday, March 27, 2011, 6:15 PM Hello,
tqtinterface build system was massively reworked.
Available options:
QT_VERSION=3 or USE_QT3 - activate Qt3 support
QT_VERSION=4 or USE_QT4 - activate Qt4 support
QT_PREFIX_DIR - the place where qt is installed default: /usr For Qt3, QT_VERSION inherits QTDIR, _if_ QTDIR environment variable is set.
QT_INCLUDE_DIR - the place where qt headers are installed default: ${QT_PREFIX_DIR}/include/qt${QT_VERSION}
QT_LIBRARY_DIR - the place of qt libraries default: ${QT_PREFIX_DIR}/lib${LIB_SUFFIX} For Qt4, libQtGui.so presence is checked, if is not exists in ${QT_PREFIX_DIR}/lib${LIB_SUFFIX}, ${QT_PREFIX_DIR}/lib${LIB_SUFFIX}/qt4 is checked as well
QT_LIBRARIES - list of qt libraries required for linking Default for Qt3 - qt-mt Default for Qt4 - QtCore QtGui
QT_BINARY_DIR - the place where qt tools are installed (moc and uic) default: ${QT_PREFIX_DIR}/bin
MOC_EXECUTABLE - absolute path to moc default: ${QT_BINARY_DIR}/moc
UIC_EXECUTABLE - absolute path to uic default: ${QT_BINARY_DIR}/uic
Note: PKGCONFIG_INSTALL_DIR is defaulted to /usr/lib${LIB_SUFFIX}/pkgconfig, to avoid tqt detection problems.
Note: these options are available only for tqtinterface, the rest of packages inherits it automatically from tqt (for example, you do not need to pass argument QT_VERSION=3 to kdelibs' cmake).
-- Serghei
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Wednesday 30 March 2011 20:04:03 Darrell Anderson wrote:
Okay, so what does all of this mean to me as 1) a packager
For packagers, I enumerated all possible options.
and 2) an end-user?
No change for end-user.
Nothing on the wiki yet. (I'll update the wiki but I haven't a clue what to write.)
I think the infos presented by me in previous email should be enough.
Are we supposed to start building Trinity using QT4 rather than QT3?
No, Qt4 is not ready for production.
Do we build for both QT3 and QT4 and whichever QT package the end-user has installed is the one Trinity will use?
No, tqt3 and tqt4 cannot coexists.
If both QT3 and QT4 is installed which gets used by Trinity when the end-user runs Trinity?
The one selected by packager when build tqt.
Darrell