Packages / Debian 13 (Trixie) / libdevel / libpetsc-complex-dev
Package: libpetsc-complex-dev
Maintainers:
External Resources:
Homepage: [www.mcs.anl.gov]
Similar packages:
- [libpetsc3.22-dev-common]
Common header and support dev files for PETSc
- [libpetsc3.22-dev-examples]
Static libraries, shared links, header files for PETSc
- [libpetsc64-complex3.22]
Shared libraries for version 3.22 of 64-bit PETSc with Complex Numbers
- [libpetsc64-complex3.22-dbg]
Debugging libraries for 64-bit PETSc with Complex Numbers
- [libpetsc64-complex3.22-dev]
Development files for 64-bit PETSc with complex numbers
- [libpetsc64-complex-dev]
Latest 64-bit PETSc development package with complex numbers
- [libpetsc64-real3.22]
Shared libraries for version 3.22 of 64-bit PETSc
- [libpetsc64-real3.22-dbg]
Debugging libraries for PETSc
- [libpetsc64-real3.22-dev]
Static libraries, shared links, header files for 64-bit PETSc
- [libpetsc64-real-dev]
Virtual package depending on latest 64-bit PETSc development package
- [libpetsc-complex3.22]
Shared libraries for version 3.22 of PETSc with Complex Numbers
- [libpetsc-complex3.22-dbg]
Debugging libraries for PETSc
- [libpetsc-complex3.22-dev]
Static libraries, shared links, header files for PETSc
- [libpetsc-real3.22]
Shared libraries for version 3.22 of PETSc
- [libpetsc-real3.22-dbg]
Debugging libraries for PETSc
- [libpetsc-real3.22-dev]
Static libraries, shared links, header files for PETSc
- [libpetsc-real-dev]
Virtual package depending on latest PETSc development package
- [petsc3.22-doc]
Documentation and examples for PETSc
- [petsc64-dev]
Virtual package depending on latest 64-bit PETSc development package
- [petsc-dev]
Virtual package depending on latest PETSc development package
Virtual package depending on latest PETSc development package
Жоден опублікований запис не відповідає цьому фільтру набору та архітектури.
Шляхи файлів пакета (0)
Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.
No package-associated file paths were observed for the displayed build metadata.
