Upstream software project

libgdiplus

Development files for libgdiplus

About libgdiplus

Development files for libgdiplus

This project links 2 native package records across 1 recorded operating-system release. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

libgdiplus repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
openSUSE Leap 15.6: 2 package records. Catalog coverage diagram, not an application screenshot.libgdiplus: recorded package coverageopenSUSE Leap 15.62 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
libgdiplus
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
opensuse-leap-15-6
License expression
(LGPL-2.1+ or MPL-1.1) and MIT
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

This library is part of the Mono project. It is required when using System.Drawing.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

openSUSE Leap 15.6

  1. Package libgdiplus0

    leap-15.6 (openSUSE Leap 15.6) (System/Libraries): Open Source Implementation of the GDI+ API

    3.12-1.9: aarch64 ppc64le s390x x86_64

    Source: libgdiplus

  2. Package libgdiplus-devel

    leap-15.6 (openSUSE Leap 15.6) (Development/Libraries/C and C++): Development files for libgdiplus

    3.12-1.9: aarch64 ppc64le s390x x86_64

    Source: libgdiplus

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.