Patrick Sanan <[email protected]> writes: > How about a plug-in PC implementation, compiled as its own dynamic library, > depending on both SLEPc and PETSc?
Of course, but such a thing would need its own continuous integration, etc.
- Re: [petsc-dev] circular dependencies SLEPc Matthew Knepley via petsc-dev
- Re: [petsc-dev] circular dependencies S... Jed Brown via petsc-dev
- Re: [petsc-dev] circular dependenci... Matthew Knepley via petsc-dev
- Re: [petsc-dev] circular depend... Jed Brown via petsc-dev
- Re: [petsc-dev] circular depend... Jed Brown via petsc-dev
- Re: [petsc-dev] circular depend... Fande Kong via petsc-dev
- Re: [petsc-dev] circular depend... Balay, Satish via petsc-dev
- Re: [petsc-dev] circular depend... Matthew Knepley via petsc-dev
- Re: [petsc-dev] circular depend... Smith, Barry F. via petsc-dev
- Re: [petsc-dev] circular dependencies SLEPc Smith, Barry F. via petsc-dev
- Re: [petsc-dev] circular dependencies S... Jed Brown via petsc-dev
- Re: [petsc-dev] circular dependenci... Jed Brown via petsc-dev
- Re: [petsc-dev] circular dependencies S... Jed Brown via petsc-dev
- Re: [petsc-dev] circular dependenci... Smith, Barry F. via petsc-dev
- Re: [petsc-dev] circular depend... Jed Brown via petsc-dev
- Re: [petsc-dev] circular depend... Smith, Barry F. via petsc-dev
- Re: [petsc-dev] circular depend... Jed Brown via petsc-dev
- Re: [petsc-dev] circular depend... Jed Brown via petsc-dev
- Re: [petsc-dev] circular depend... Matthew Knepley via petsc-dev
- Re: [petsc-dev] circular depend... Pierre Jolivet via petsc-dev
- Re: [petsc-dev] circular depend... Smith, Barry F. via petsc-dev
