12 Mar
2012
12 Mar
'12
3:44 a.m.
On 03/11/2012 12:42 PM, Darrell Anderson wrote:
Should we report Qt3 bugs or has all focus now shifted
to TQt3?
Yesterday I successfully built all of my packages against TQt3. Today I tried to build
against Qt3 and tdebase failed with the following:
/dev/shm/tdebase.build/kicker/kicker/core/kmenubase.ui.h:7: error: 't_xdisplay'
was not declared in this scope
Reports these errors or abandon building against Qt3?
Darrell
My understanding is YES. Looking at the GIT Qt3 and TQt3 setup, TQt3 is
apparently updated from Qt3 (a smart way to maintain both). So if there is a Qt3
bug, then it should be reported so that it will be pulled into TQt3.
If my understanding on how this works is correct, then we should continue to
maintain in this fashion until we hit a milestone that makes it no longer
possible. (some reason why TQt3 can no longer pull from Qt3). It just insures
consistency between the two and cuts maintaining the core Qt3 in half.
It would suck to have to maintain both separately.
--
David C. Rankin, J.D.,P.E.