Re: [trinity-devel] Bugs, bugs, bugs

Sounds like a good idea to me. But... Is the current effort toward supporting cmake negating building with automake? That is, can svn still be built with automake scripts or is that option now a dead end? The wiki seems to contain the information I need to rewrite my build scripts, but I'm no developer and will need time to make that transition and fully test. The wiki states that only a handful of packages are fully tested with cmake. Does that mean Trinity is in no man's land right now with respect to building all packages? Or do some packages have to be built with cmake and others with automake? Or can either build process be used? If I no longer can build with automake then I have to learn about cmake and revise all of my build scripts. My challenge is if automake no longer is supported in svn, then I am unable to help test any patches. If I can still build svn with automake then I'll help test patches. Side note to developers: please do not automatically close a report until the original filer reports the status of the patch. Let's build quality software and not just count beans. :) Also note in the bugzilla all packages that need to be rebuilt to test a specific bug report. A bug report might related to one app, but might require rebuilding more than one package. Notice that even with a dual core machine, building the entire suite of core packages and a handful of others requires about five to six hours. Testing patches will take time, especially when new build problems arise. Darrell --- On Fri, 3/4/11, Timothy Pearson <kb9vqf(a)pearsoncomputing.net> wrote: