Configured and installed version qt3 tag v3.5.13:
./configure -prefix /home/midenok/src/kde/opt -I/usr/include/freetype2 -debug -shared -qt-gif -thread -sm -system-zlib -system-libpng -system-libjpeg make install
Configured and installed tqtinterface tag v3.5.13, admin/ at e4edddce0ad, cmake/ at ae53051703d:
mkdir -p build.debug cd build.debug opt_dir=/home/midenok/src/kde/opt
export PATH=/home/midenok/src/kde/opt/bin:$PATH
cmake .. \ -DCMAKE_BUILD_TYPE=Debug \ -DCMAKE_INSTALL_PREFIX=${opt_dir} \ -DPKGCONFIG_INSTALL_DIR=${opt_dir}/lib/pkgconfig \ -DQT_VERSION=3 \ -DQT_PREFIX_DIR=${opt_dir} \ -DQT_INCLUDE_DIR=${opt_dir}/include \ -DQT_BINARY_DIR=${opt_dir}/bin
make install
Configured tdelibs tag v3.5.13, admin/ at e4edddce0ad, cmake/ at ae53051703d:
opt_dir=/home/midenok/src/kde/opt
export PATH=$opt_dir/bin:$PATH export LD_LIBRARY_PATH=$opt_dir/lib:$LD_LIBRARY_PATH export PKG_CONFIG_PATH=$opt_dir/lib/pkgconfig
mkdir -p build.debug cd build.debug cmake .. \ -DCMAKE_BUILD_TYPE=Debug \ -DCMAKE_INSTALL_PREFIX=$opt_dir \ -DCMAKE_VERBOSE_MAKEFILE=OFF \ -DWITH_ARTS=OFF
make
[ 18%] Building CXX object kdeui/CMakeFiles/kdeui-shared.dir/kshortcutdialog_simple.cpp.o /home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp: In constructor ‘KShortcutDialogSimple::KShortcutDialogSimple(QWidget*, const char*)’: /home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp:31:50: error: invalid use of incomplete type ‘struct QLabel’
On Tue, Feb 14, 2012 at 12:29 PM, Aleksey Midenkov midenok@gmail.com wrote:
[ 18%] Building CXX object kdeui/CMakeFiles/kdeui-shared.dir/kshortcutdialog_simple.cpp.o /home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp: In constructor ‘KShortcutDialogSimple::KShortcutDialogSimple(QWidget*, const char*)’: /home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp:31:50: error: invalid use of incomplete type ‘struct QLabel’
Are there some kind soul that wants to help me with that? Please!
On Tue, Feb 14, 2012 at 12:29 PM, Aleksey Midenkov midenok@gmail.com wrote:
[ 18%] Building CXX object kdeui/CMakeFiles/kdeui-shared.dir/kshortcutdialog_simple.cpp.o /home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp: In constructor KShortcutDialogSimple::KShortcutDialogSimple(QWidget*, const char*): /home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp:31:50: error: invalid use of incomplete type struct QLabel
Are there some kind soul that wants to help me with that? Please!
That looks like a problem with the ui compiler. I remember something similar happening in the past on a non-Debian distribution; Darrell Anderson on this list may be able to help with the problem if I remember correctly.
Obviously this either will be or has been fixed in GIT for R14.0. :-)
Tim
On Wed, Feb 15, 2012 at 11:01 AM, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
On Tue, Feb 14, 2012 at 12:29 PM, Aleksey Midenkov midenok@gmail.com wrote:
[ 18%] Building CXX object kdeui/CMakeFiles/kdeui-shared.dir/kshortcutdialog_simple.cpp.o /home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp: In constructor ‘KShortcutDialogSimple::KShortcutDialogSimple(QWidget*, const char*)’: /home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp:31:50: error: invalid use of incomplete type ‘struct QLabel’
Are there some kind soul that wants to help me with that? Please!
That looks like a problem with the ui compiler. I remember something similar happening in the past on a non-Debian distribution; Darrell Anderson on this list may be able to help with the problem if I remember correctly.
Obviously this either will be or has been fixed in GIT for R14.0. :-)
I suppose, that if there is the tag in Git for v3.5.13, then it *must* be buildable. If it is not so, then one of two things happened:
1. the actual release was not build from that tag exactly as it is, there were some hand made fixes, that are not reflected in the tag 2. the tag was placed after the release and points not exactly to the release point
Absence of the tag for admin/ and cmake/ submodules brings me to assumption of p.2. In either case the tag is wrong and must be fixed! Or any newcomer programmers like me will be highly frustrated... :-(
On Wed, 15 Feb 2012 01:01:10 -0600 "Timothy Pearson" kb9vqf@pearsoncomputing.net wrote:
On Tue, Feb 14, 2012 at 12:29 PM, Aleksey Midenkov midenok@gmail.com wrote:
[ 18%] Building CXX object kdeui/CMakeFiles/kdeui-shared.dir/kshortcutdialog_simple.cpp.o /home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp: In constructor ‘KShortcutDialogSimple::KShortcutDialogSimple(QWidget*, const char*)’: /home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp:31:50: error: invalid use of incomplete type ‘struct QLabel’
Are there some kind soul that wants to help me with that? Please!
That looks like a problem with the ui compiler. I remember something similar happening in the past on a non-Debian distribution; Darrell Anderson on this list may be able to help with the problem if I remember correctly.
IIRC you have to do $ export PATH=/trinity/prefix/bin:$PATH before building Trinity, oherwise you could be using the Qt4 uic.
Obviously this either will be or has been fixed in GIT for R14.0. :-)
Tim
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Wed, Feb 15, 2012 at 4:12 PM, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
On Wed, 15 Feb 2012 01:01:10 -0600 "Timothy Pearson" kb9vqf@pearsoncomputing.net wrote:
On Tue, Feb 14, 2012 at 12:29 PM, Aleksey Midenkov midenok@gmail.com wrote:
[ 18%] Building CXX object kdeui/CMakeFiles/kdeui-shared.dir/kshortcutdialog_simple.cpp.o /home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp: In constructor ‘KShortcutDialogSimple::KShortcutDialogSimple(QWidget*, const char*)’: /home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp:31:50: error: invalid use of incomplete type ‘struct QLabel’
Are there some kind soul that wants to help me with that? Please!
That looks like a problem with the ui compiler. I remember something similar happening in the past on a non-Debian distribution; Darrell Anderson on this list may be able to help with the problem if I remember correctly.
IIRC you have to do $ export PATH=/trinity/prefix/bin:$PATH before building Trinity, oherwise you could be using the Qt4 uic.
In fact, it has used uic from preinstalled qt3-dev-tools. And that is because tqtinterface found it there on configuration phase and installed tqt.pc that pointed to /usr/bin/uic-qt3 and /usr/bin/moc-qt3. After uninstalling qt3-dev-tools and reconfiguring tqtinterface it become pointing to $opt_dir/bin/uic and $opt_dir/bin/moc. Which is right because they are installed from Git version of qt3. But nevertheless, the error stays the same!
Trying to reconfigure tdelibs for uic-tqt and moc-tqt makes worse error:
cd /home/midenok/src/kde/tdelibs/build.debug/kdeui && /usr/bin/cmake -DUIC_EXECUTABLE:FILEPATH=/home/midenok/src/kde/opt/bin/uic-tqt -DTDE_QTPLUGINS_DIR:FILEPATH= -DUI_FILE:FILEPATH=/home/midenok/src/kde/tdelibs/kdeui/kshortcutdialog_advanced.ui -P /home/midenok/src/kde/tdelibs/cmake/modules/tde_uic.cmake cd /home/midenok/src/kde/tdelibs/build.debug/kdeui && /home/midenok/src/kde/opt/bin/moc-tqt kshortcutdialog_advanced.h >> kshortcutdialog_advanced.cpp
cp: missing destination file operand after `.bkp' Try `cp --help' for more information.
That is because moc-tqt accepts different arguments than moc. I'm totally perplexed with these three versions: moc, tmoc, moc-tqt. What must be used in tdelibs?
[ 18%] Building CXX object
kdeui/CMakeFiles/kdeui-shared.dir/kshortcutdialog_simple.cpp.o
/home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp:
In constructor
‘KShortcutDialogSimple::KShortcutDialogSimple(QWidget*, const
char*)’:
/home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp:31:50:
error: invalid use of incomplete type
‘struct QLabel’
Are there some kind soul that wants to help me
with that? Please!
That looks like a problem with the ui compiler. I
remember something
similar happening in the past on a non-Debian
distribution; Darrell
Anderson on this list may be able to help with the
problem if I
remember correctly.
IIRC you have to do $ export PATH=/trinity/prefix/bin:$PATH before building Trinity, oherwise you could be using the Qt4 uic.
Obviously this either will be or has been fixed in GIT
for R14.0. :-)
I don't know how much I can help here. :)
I believe the reference to me might be to the time I had to troubleshoot certain build failures, which eventually I discovered were caused be setting the $CPLUS_INCLUDE_PATH environment variable. Setting the $CPLUS_INCLUDE_PATH in the build environment prevents pkg-config from running properly. The moment I removed that export command in my master script, the cmake TQT_INCLUDE_DIRS internal variable began populating automatically.
First and foremost, I use a chroot environment to build Trinity packages. In that environment I do not have KDE3, KDE4, or Qt4 installed. For my usability testing I might have any or all of those three installed, but not in my build environment. An alternative to a chroot environment is a virtual machine or a separate physical machine. The idea is to have a clean but full distro installation minus anything that will cause conflicts. For example, proprietary video drivers should never be installed in a Trinity build environment.
For my usability testing I do not use my chroot build environment. Instead I use virtual machines and separate partitions on physical machines. I keep my usability testing environments separate from my build environment.
As mentioned in the wiki, I install all Trinity packages, including (T)Qt3, to /opt/trinity except tqtinterface. I install tqtinterface to /usr.
To avoid conflicts with Qt4, in all build scripts still using automake, I explicitly define where to find Qt3 files:
--with-qt-dir=${QTDIR} --with-qt-includes=${QT_INCLUDE_DIR} --with-qt-libraries=${QTDIR}/lib
The cmake builds do not need those same explicit declarations (those locations are now built into the Trinity cmake build process). Of course, in my build environment I remove the Qt4 package and avoid conflicts altogether. However, I maintain these explicit declarations as habit because originally one of the project goals was to build certain packages with Qt4 support. That is not the case today, but I maintain the explicit declarations. A clean and separate build environment more or less avoids all of these issues.
I explicitly define in my master build script certain environment variables, such as $PATH. The search path must include the Trinity bin directory first in the $PATH variable, and not appended last as is standard practice.
With building (T)Qt3, no related build environment variables are yet set because that is the first package built in the entire build sequence. However, in my (T)Qt3 build script I explicitly declare two environment variables because the Qt3 build process dependes upon its own binaries to build:
export QTDIR=`pwd` if [ -n "$LD_LIBRARY_PATH" ]; then export LD_LIBRARY_PATH=${QTDIR}/lib:$LD_LIBRARY_PATH else export LD_LIBRARY_PATH=${QTDIR}/lib fi export PATH=${QTDIR}/bin:$PATH
As much as building the entire package set in automated mode is desirable, I have not figured out a way to do so until I have both (T)Qt3 and tqtinterface built. Thereafter I can build all other packages in automated mode. Therefore I first build and install (T)Qt3. Then I build and install tqtinterface. Thereafter I build everything else in automated mode.
After I have (T)Qt3 and tqtinterface installed, my master build script explicitly sets the following environment variables:
$PKG_CONFIG_PATH $QTDIR $QT_INCLUDE_DIR $QT_LIB_DIR $LD_LIBRARY_PATH $PATH
I am in the process today of building everything from scratch from GIT for the first time in a few weeks. We'll see how that goes by the end of the day.
I hope something here helps. :)
Darrell
Thanks this info helped me a little. I am building from a slackware base with only lxde installed. For me evertyhing seems to build until i pulled the latest git a few days ago. Now my autobuilds don't find qt3, and avahi-tqt will not build because of a 'too many arguments' moc error. Without avahi-tqt (and i only use Qt3) i have a usable desktop environment with avahi and zeroconf functioning.
Please keep us updated of any problems you may find with this latest build session.
Thanks.
On Wed, Feb 15, 2012 at 10:00 PM, Darrell Anderson humanreadable@yahoo.comwrote:
[ 18%] Building CXX object
kdeui/CMakeFiles/kdeui-shared.dir/kshortcutdialog_simple.cpp.o
/home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp:
In constructor
‘KShortcutDialogSimple::KShortcutDialogSimple(QWidget*, const
char*)’:
/home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp:31:50:
error: invalid use of incomplete type
‘struct QLabel’
Are there some kind soul that wants to help me
with that? Please!
That looks like a problem with the ui compiler. I
remember something
similar happening in the past on a non-Debian
distribution; Darrell
Anderson on this list may be able to help with the
problem if I
remember correctly.
IIRC you have to do $ export PATH=/trinity/prefix/bin:$PATH before building Trinity, oherwise you could be using the Qt4 uic.
Obviously this either will be or has been fixed in GIT
for R14.0. :-)
I don't know how much I can help here. :)
I believe the reference to me might be to the time I had to troubleshoot certain build failures, which eventually I discovered were caused be setting the $CPLUS_INCLUDE_PATH environment variable. Setting the $CPLUS_INCLUDE_PATH in the build environment prevents pkg-config from running properly. The moment I removed that export command in my master script, the cmake TQT_INCLUDE_DIRS internal variable began populating automatically.
First and foremost, I use a chroot environment to build Trinity packages. In that environment I do not have KDE3, KDE4, or Qt4 installed. For my usability testing I might have any or all of those three installed, but not in my build environment. An alternative to a chroot environment is a virtual machine or a separate physical machine. The idea is to have a clean but full distro installation minus anything that will cause conflicts. For example, proprietary video drivers should never be installed in a Trinity build environment.
For my usability testing I do not use my chroot build environment. Instead I use virtual machines and separate partitions on physical machines. I keep my usability testing environments separate from my build environment.
As mentioned in the wiki, I install all Trinity packages, including (T)Qt3, to /opt/trinity except tqtinterface. I install tqtinterface to /usr.
To avoid conflicts with Qt4, in all build scripts still using automake, I explicitly define where to find Qt3 files:
--with-qt-dir=${QTDIR} --with-qt-includes=${QT_INCLUDE_DIR} --with-qt-libraries=${QTDIR}/lib
The cmake builds do not need those same explicit declarations (those locations are now built into the Trinity cmake build process). Of course, in my build environment I remove the Qt4 package and avoid conflicts altogether. However, I maintain these explicit declarations as habit because originally one of the project goals was to build certain packages with Qt4 support. That is not the case today, but I maintain the explicit declarations. A clean and separate build environment more or less avoids all of these issues.
I explicitly define in my master build script certain environment variables, such as $PATH. The search path must include the Trinity bin directory first in the $PATH variable, and not appended last as is standard practice.
With building (T)Qt3, no related build environment variables are yet set because that is the first package built in the entire build sequence. However, in my (T)Qt3 build script I explicitly declare two environment variables because the Qt3 build process dependes upon its own binaries to build:
export QTDIR=`pwd` if [ -n "$LD_LIBRARY_PATH" ]; then export LD_LIBRARY_PATH=${QTDIR}/lib:$LD_LIBRARY_PATH else export LD_LIBRARY_PATH=${QTDIR}/lib fi export PATH=${QTDIR}/bin:$PATH
As much as building the entire package set in automated mode is desirable, I have not figured out a way to do so until I have both (T)Qt3 and tqtinterface built. Thereafter I can build all other packages in automated mode. Therefore I first build and install (T)Qt3. Then I build and install tqtinterface. Thereafter I build everything else in automated mode.
After I have (T)Qt3 and tqtinterface installed, my master build script explicitly sets the following environment variables:
$PKG_CONFIG_PATH $QTDIR $QT_INCLUDE_DIR $QT_LIB_DIR $LD_LIBRARY_PATH $PATH
I am in the process today of building everything from scratch from GIT for the first time in a few weeks. We'll see how that goes by the end of the day.
I hope something here helps. :)
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Thu, Feb 16, 2012 at 2:00 AM, Darrell Anderson humanreadable@yahoo.com wrote:
[ 18%] Building CXX object
kdeui/CMakeFiles/kdeui-shared.dir/kshortcutdialog_simple.cpp.o
/home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp:
In constructor
‘KShortcutDialogSimple::KShortcutDialogSimple(QWidget*, const
char*)’:
/home/midenok/src/kde/tdelibs/build.debug/kdeui/kshortcutdialog_simple.cpp:31:50:
error: invalid use of incomplete type
‘struct QLabel’
Are there some kind soul that wants to help me
with that? Please!
That looks like a problem with the ui compiler. I
remember something
similar happening in the past on a non-Debian
distribution; Darrell
Anderson on this list may be able to help with the
problem if I
remember correctly.
IIRC you have to do $ export PATH=/trinity/prefix/bin:$PATH before building Trinity, oherwise you could be using the Qt4 uic.
Obviously this either will be or has been fixed in GIT
for R14.0. :-)
I don't know how much I can help here. :)
Looks like I must troubleshoot this myself... :) But anyway, please tell what is the difference between moc, tmoc and moc-tqt and what is meant to be called in build process? Someone must know this for sure!
And please fix tag v3.5.13 for /admin and /cmake submodules (to commits mentioned in first post).
-
/dev/ammo42 -
Aleksey Midenkov -
Darrell Anderson -
Jay -
Timothy Pearson