trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: March 2012

Re: [trinity-devel] tqt3 api/abi update

From: Darrell Anderson <humanreadable@...>
Date: Sat, 10 Mar 2012 11:51:38 -0800 (PST)
> I guess you meant starting over completely this am. Because
> I still get:
> 
> [ 11%] Building CXX object
> libtdepim/CMakeFiles/tdepim-shared.dir/kscoringeditor.cpp.o
> cd /build/src/build/libtdepim &&
> /usr/bin/c++   -Dtdepim_shared_EXPORTS
> -D_FILE_OFFSET_BITS=64 -DHAVE_CONFIG_H -march=x86-64
> -mtune=generic -O2 -pipe
> -fstack-protector --param=ssp-buffer-size=4
> -D_FORTIFY_SOURCE=2
> -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL
> -DQT_NO_COMPAT
> -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT
> -include tqt.h -fPIC
> -I/build/src/build/libtdepim -I/build/src/build
> -I/build/src/tdepim
> -I/build/src/tdepim/libtdepim -I/opt/trinity/include
> -I/opt/tqt3/include
> -I/opt/trinity/include/tqt    -o
> CMakeFiles/tdepim-shared.dir/kscoringeditor.cpp.o -c
> /build/src/tdepim/libtdepim/kscoringeditor.cpp
> /build/src/tdepim/libtdepim/kscoringeditor.cpp: In member
> function 'void
> SingleConditionWidget::showRegExpDialog()':
> /build/src/tdepim/libtdepim/kscoringeditor.cpp:140:91:
> error: 'class TQDialog'
> has no member named 'tqt_cast'
> make[2]: ***
> [libtdepim/CMakeFiles/tdepim-shared.dir/kscoringeditor.cpp.o]
> Error 1
> make[2]: Leaving directory `/build/src/build'
> make[1]: *** [libtdepim/CMakeFiles/tdepim-shared.dir/all]
> Error 2
> make[1]: Leaving directory `/build/src/build'
> make: *** [all] Error 2
> ==> ERROR: A failure occurred in build().
>     Aborting...
> ==> ERROR: Build failed, check
> /mnt/nv1/home/chroot/david/build

Whenever Tim plays his tqt tweaking fiddle, I always rebuild everything, starting with TQt3. I am sure that is not always required, but I have lots to do while TQt3 rebuilds for 20 minutes in the background. :)

When the bug fixes do not involve TQt3 or tqtinterface, then I rebuild starting with the first affected package. Often I'll grab the single patch and apply the patch to the affected package. Within a few days I typically rebuild everything from scratch and then discard the singlular patch.

I realize that rebuilding from scratch can be a potential PITA, but to me is cleaner and less complicated.

As I mentioned in another post, I use virtual machines for my basic testing. So for me rebuilding is not a hindrance as my everyday production desktop is unaffected.

Darrell