On 12 December 2013 19:06, Satish Balay <[email protected]> wrote: > On Thu, 12 Dec 2013, Lisandro Dalcin wrote: > >> On 12 December 2013 18:03, Todd Munson <[email protected]> wrote: >> > >> > The idea is to distribute TAO with PETSc and treat it like any other set >> > of PETSc solves. >> > All the TaoLog (or TaoNewLog) macros should go away in my opinion and be >> > replace with >> > the correct PETSc equivalents. >> > >> > Jason? >> > >> > Todd. >> > >> >> Not sure if you guys care about previous PETSc releases, but #define >> TaoNew[Log] would ease supporting petsc-3.4 in the next TAO release. > > There won't be a next [standalone] tao release. It will be part of > petsc-3.5. >
Oh! I didn't know... Very good news.... > > And I'm not sure if maintaining a separate tao_version.h makes sense. > Probably not.... > And there will be a minimal changing of adapting the makefiles to to > this new mode [if one needs to maintain comatibility with > both petsc-3.4+tao-2.2 and petsc-3.5/tao]. > > You can check the current state of this migration at 'balay/tao-to-petsc' > branch. > I guess this should doable. >> In PetIGA, I'm currently supporting petsc-3.3, petsc-3.4 and master. > > Does PetIGA also use tao [multiple versions?] > No, PetIGA does not depend on TAO. I was trying to point out that supporting older PETSc releases is doable. -- Lisandro Dalcin --------------- CIMEC (UNL/CONICET) Predio CONICET-Santa Fe Colectora RN 168 Km 472, Paraje El Pozo 3000 Santa Fe, Argentina Tel: +54-342-4511594 (ext 1016) Tel/Fax: +54-342-4511169
