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@...> wrote: > From: Timothy Pearson <kb9vqf@...> > Subject: Re: [trinity-devel] Bugs, bugs, bugs > To: trinity-devel@... > Date: Friday, March 4, 2011, 4:18 PM > On 03/04/2011 12:33 PM, Calvin > Morrison wrote: > > Darrell, > > > > Your call to arms is quite convincing. A bug squashing > day is in order. > > OK, I fully agree here. My concern with CMake being > incomplete was that people who would otherwise be able to > help squash bugs may not be able to because they can't get > Trinity to build and/or install. > > Let's do this: Everyone who can get Trinity to build > and install from SVN please do so ASAP. I'll give > everyone a week or so to do this. > > Then, on 03/12/2011 or thereabouts, let's all gather on IRC > and start hammering away at the bugs. I'll be there to > offer any help on locating the problematic sections of code, > and may even chip in some patches myself depending on time. > > If the 12th does not work I'd like to hear some other > suggestions :) The goal will be to create patches for > as many bugs as possible on the bugtracker; patches can be > posted on the appropriate bug reports for a large batch > commit by samelian and I after reviewing them. > > Does this sound like a good idea? > > Tim > > --------------------------------------------------------------------- > To unsubscribe, e-mail: trinity-devel-unsubscribe@... > For additional commands, e-mail: trinity-devel-help@... > Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ > Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting > >