Packages / openSUSE Tumbleweed / level-zero-devel

Package: level-zero-devel (1.32.0-1.2)

Entwicklungs-Paket für oneAPI Level Zero Specification Headers and Loader

Das Paket level-zero-devel enthält Bibliotheks- und Header-Dateien zur Entwicklung von Anwendungen, die level-zero verwenden.

Package information

Homepage
[https://github.com/oneapi-src/level-zero]
License
MIT
Downstream-Paketbetreuer
Unbekannt: in der indizierten Quelle nicht gemeldet
Quellpaket
[level-zero]
Software project
[level-zero]

Versions and downloads for level-zero-devel

Version / releaseArchitecture / repositoryPackage sizeInstalled sizeFilesPublisher repository artifact
1.32.0-1.2tumbleweed / ossx86_64openSUSE Tumbleweed · OSS · multi-architecture179 KiB2.4 MiBlist of fileslevel-zero-devel-1.32.0-1.2.x86_64.rpm
About these downloads

Jede Zeile ist Paketindex-Metadaten für eine Version, Architektur, Suite und ein Repository. Namen, URLs und Größen stammen aus der Quelle; ein Link ist ein veränderbarer Abrufort, kein Weitergabanspruch von OpenFactory.

Other packages built from level-zero

  • level-zero

    oneAPI Level Zero Spezifikations-Header und Loader

Dependencies and recommendations for level-zero-devel

  • dep: /usr/bin/pkg-config

    Package not available

  • dep: [level-zero] (= 1.32.0-1.2)

    oneAPI Level Zero Spezifikations-Header und Loader

  • dep: pkgconfig(libze_loader)

    Package not available

Paketdateipfade (21)

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.

  • /usr/include/level_zero
  • /usr/include/level_zero/layers
  • /usr/include/level_zero/layers/zel_tracing_api.h
  • /usr/include/level_zero/layers/zel_tracing_ddi.h
  • /usr/include/level_zero/layers/zel_tracing_register_cb.h
  • /usr/include/level_zero/loader
  • /usr/include/level_zero/loader/ze_loader.h
  • /usr/include/level_zero/ze_api.h
  • /usr/include/level_zero/ze_ddi_common.h
  • /usr/include/level_zero/ze_ddi.h
  • /usr/include/level_zero/zer_api.h
  • /usr/include/level_zero/zer_ddi.h
  • /usr/include/level_zero/zes_api.h
  • /usr/include/level_zero/zes_ddi.h
  • /usr/include/level_zero/zet_api.h
  • /usr/include/level_zero/zet_ddi.h
  • /usr/lib64/libze_loader.so
  • /usr/lib64/libze_tracing_layer.so
  • /usr/lib64/libze_validation_layer.so
  • /usr/lib64/pkgconfig/level-zero.pc
  • /usr/lib64/pkgconfig/libze_loader.pc

Field source: openSUSE Tumbleweed OSS

Bekannte Sicherheitslücken

Keine passenden Meldungen in den erfassten Quellen.

Zuletzt synchronisiert:

[CVE-Katalog]

Prüfsummen

Repository signatures authenticate metadata. Artifact hashing is recorded separately. Neither establishes package safety.

1.32.0-1.2 / x86_64Beobachtet Sep 1, 2026sha512 beded11c7b80…04a429b7Prüfsumme der Quelle

Metadata observed; artifact bytes were not independently fetched or hashed by this catalog import. The digest below is source-reported.

Prüfsumme der Quelle (sha512): beded11c7b801b5c647fd88a82c4eb55b09183e8896ba9f5ae8e81041ed50d35f6d2a0a977398f5cc377c4c4b9c907924d860d326f082e8a29d5c15e04a429b7

Field source: openSUSE Tumbleweed OSS

Quellen

  • Authoritative source; repository metadata signature verified

    Signaturnachweis

    tumbleweed-oss-multiarch:4db10cdde3ad82c7e22be35753c9e164b4bdd30f92db4aee17a0d4c94c5f902f

    Repository-signature verification record
    Signed-object SHA-256
    4db10cdde3ad82c7e22be35753c9e164b4bdd30f92db4aee17a0d4c94c5f902f
    Signer fingerprint
    AD485664E901B867051AB15F35A2F86E29B700A4
    Keyring revision
    opensuse-project-signing-key.asc
    SHA-256 b5745739ebfb95b25b8e810f9bcb847fe750ccda598bd85f02f0e974599a6d7e
    Tool and policy
    gpgv (GnuPG) 2.4.9
    openfactory-software-catalog-signature-v1
    Verification time
    Sep 1, 2026
    Repository metadata hash linkage
    Result
    Recorded as verified; digest details unavailable

Dieses Paket verwenden

OpenFactory kann dieses Betriebssystem in einer Browser-VM starten oder einen Image-Build mit dem nativen Paketnamen aus diesem Datensatz beginnen.