Upstream software project

toml11

Development files for toml11

About toml11

Development files for toml11

This project links 7 native package records across 7 recorded operating-system releases. 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

toml11 repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Leap 15.6: 1 package records; openSUSE Leap 16.0: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.toml11: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsFedora 431 recordsFedora 441 recordsopenSUSE Leap 15.61 recordsopenSUSE Leap 16.01 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
toml11
Publisher
Not authoritatively mapped
Native package records
7
Operating systems
debian-12, debian-13, fedora-43, fedora-44, opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
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.

toml11 is a C++11 (or later) header-only toml parser/encoder depending only on C++ standard library. * It is compatible to the latest version of TOML v1.0.0. * It is one of the most TOML standard compliant libraries, tested with the language agnostic test suite for TOML parsers by BurntSushi. * It shows highly informative error messages. You can see the error messages about invalid files at CircleCI. * It has configurable container. You can use any random-access containers and key-value maps as backend containers. * It optionally preserves comments without any overhead. * It has configurable serializer that supports comments, inline tables, literal strings and multiline strings. * It supports user-defined type conversion from/into toml values. * It correctly handles UTF-8 sequences, with or without BOM, both on posix and Windows. Development files for toml11.

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.

Debian 12 (Bookworm)

  1. Package libtoml11-dev

    bookworm (Debian 12 (Bookworm)) (libdevel): TOML parser/encoder

    3.7.1-3: all

    Source: toml11

Debian 13 (Trixie)

  1. Package libtoml11-dev

    trixie (Debian 13 (Trixie)) (libdevel): TOML parser/encoder

    4.4.0-1: all

    Source: toml11

Fedora 43

  1. Package toml11-devel

    43 (Fedora 43) (Unspecified): Development files for toml11

    4.4.0-2.fc43: aarch64 i686 x86_64

    Source: toml11

Fedora 44

  1. Package toml11-devel

    44 (Fedora 44) (Unspecified): Development files for toml11

    4.4.0-3.fc44: aarch64 i686 x86_64

    Source: toml11

openSUSE Leap 15.6

  1. Package toml11-devel

    leap-15.6 (openSUSE Leap 15.6) (Unspecified): Development files for toml11

    3.7.1-bp156.1.2: aarch64 ppc64le s390x x86_64

    Source: toml11

openSUSE Leap 16.0

  1. Package toml11-devel

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Development files for toml11

    3.7.1-bp160.1.10: aarch64 ppc64le s390x x86_64

    Source: toml11

openSUSE Tumbleweed

  1. Package toml11-devel

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Development files for toml11

    4.4.0-1.4: x86_64

    Source: toml11

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.