trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2014

Re: [trinity-devel] cmake conversion audit

From: "Darrell Anderson" <darrella@...>
Date: Tue, 11 Feb 2014 22:08:56 -0600
>Perhaps it is worth do a complete check of what is completed and 
>what not. That means check every single package.

I agree. How?

For example, dolphin was listed in the etherpad as completed. Yet I 
compiled dolphin with cmake and no doc or po files were compiled. 
Therefore I deleted the 'completed' tag in the etherpad and wrote a 
note.

I know that not all components of amarok were converted and I filed 
a bug report against that a very long time ago.

As I mentioned, the cmake packages do not build man pages. Another 
bug report filed.

This is part of why I am suspicious of whether all packages have 
been converted completely.

To my knowledge we no longer can build the core packages with 
automake. Only cmake. Therefore the only file-by-file comparison we 
can attempt is with a fully compiled 3.5.13.2 package. We have to 
account for the renaming changes. Yet everybody builds packages 
differently. Using a 3.5.13.2 package as a baseline does not mean 
all components were compiled.

Darrell