4 Mar
2012
4 Mar
'12
8:31 p.m.
On 03/04/2012 02:14 PM, Timothy Pearson wrote:
This is part of the plan already. :-) I envision at least part of that to
be a soft freeze, where any bugs found during the freeze can be patched,
but nothing else can be touched.
Also, I hope that once everything is building again on TQt3 (which should
be very quickly) , the other developers here will start looking at the
bugtracker again and send in more patches. ;-)
Tim
That would definitely explain it. I have found
CMake to be very, very
reliable compared to Autotools (though this may just be due to the
quality
of the work that Serghei did :-)), and usually problems that show up in
the CMake builds are due to code problems or operator error. ;-)
Tim
I have been absolutely amazed at how brilliantly TDE is building. After
going
through the pain of transferring all the build scripts to use TQt3 and
picking
through all the patches.tar.bz2 files to eliminate unneeded patches, TDE
is
building great. I can't wait to actually load it on a box and try it :)
The challenge will be finishing the cmake conversion for the applications
and
other packages so that all apps, addons, plugins, styles, decorations,
etc.. are
building as well. It will just take time, but it is coming along.
It would be great to get to a point where the major transitions (eg: from
Qt to
TQt, etc..) is done and troubleshot -- to spend 30 days under a
code-freeze and
just work on getting all the applications, addons, etc.. building. Those
little
'niceties' are what has always make kde3 stand out as a desktop. It will
do the
same for TDE as well.