Message: previous - next
Month: April 2011

Re: [trinity-devel] Attn Tim: New Patches

From: "Timothy Pearson" <kb9vqf@...>
Date: Thu, 28 Apr 2011 13:14:43 -0500
> Hi Hello! everyone.
> in this fashion API changes these days, I found that debian and
> winbuntu old lasted revisions, has old libpng 1.2, especialy lenny
> with 1.2.22, which means that the patchs for libpng 1.4 support on qt3
> for trinity can make impossible compile into Debian squeeze, testing
> inlcusive, as win-buntu 9.XX, it should be modified to use a macro
> -LIB_PNG_14 or something similar .. I do not remember how to work with
> this but if I can do for the weekend..
> If some body can do that , please change the patch for use optionaly
> both library versions...
> If i can resolve all issues, i do a qt3 3.3.c tar gzipped release
> alternate for ready download in public, for easy acces to novice
> developers
> On Fri, Apr 1, 2011 at 4:40 PM, Darrell Anderson
> <humanreadable@...> wrote:
>> Tim,
>> Here are a bunch of patches I don't think have been merged into Trinity.
>> I checked them against svn (my head hurts!). I might have missed a few
>> because of the changes to run through tqtinterface, but not many if I
>> did.
>> Some of them will need to be converted to using TQT.
>> I found these patches while building KDE 3.5.10 on Slackware 13.1. There
>> were many more patches, but those I did not post have been merged into
>> Trinity.
>> There are quite a few patches against qt3. Several apps include patches
>> for libpng 1.4.
>> Darrell
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> trinity-devel-unsubscribe@...
>> For additional commands, e-mail:
>> trinity-devel-help@...
>> Read list messsages on the Web archive:
>> Please remember not to top-post:

I don't want to do wholesale patching of the Trinity source until I can
build at least the base modules (including kdegraphics/kdenetwork/etc.) in
a batch, which means that CMake has to progress a bit more before I can
really deal with them.

This is because it is very easy to introduce compilation and functionality
errors when applying patches, and without an immediate rebuild test and
functionality check it can be very hard to narrow down exactly what went
wrong where at some future date.

Thanks for bringing them to my attention though!