>> > For the past two days I have built the full main suite >> and a dozen additional packages from each day's latest GIT. >> I built against Qt3 and not TQt3. Regarding TQt3, Tim is >> working on some bugs some of us are experiencing when >> building against TQt3. >> > >> > Note: tdebindings will not build against Qt3 and hasn't >> built against Qt3 for a long time. Only TQt3. >> >> So you suggest TQt3 only as a base for building TDE? >> What difference does it >> make for the desktop? All styles, themes, functionality >> still the same when >> based on TQt3? > > I wasn't recommending anything, only sharing my recent experience. :) > > Currently building against TQt3 is broken. Tim will post when he has that > fixed. Until then use Qt3. :) > > Tim will have to explain the difference between TQt3 and Qt3. I don't know > whether the latter will be dropped eventually. However, as tdebindings > will not build against Qt3 and Tim has stated he will not fix the problem, > that means tdebindings will build only against TQt3 (when fixed). That > more or less makes Qt3 obsolete for anybody wanting to build tdebindings. > > Clear as mud, right? :) > > Darrell TQt3 allows the TDE developers to use Qt4 libraries within TDE applications, e.g. Webkit. Qt3 does not allow this due to C++ namespace conflicts (technically it is a problem with both the compiler and linker caused by two different definitions of common classes such as QObject, but the previous description gets the point across in a succinct manner). I strongly recommend using tqt3 if posssible, but am keeping qt3 compatibility via tqtinterface for everything except the language bindings modules (tdebindings, python-tqt, etc.). Does this help? Tim