
Upstream software project
concurrentqueue
Development files for moodycamel-concurrentqueue
About concurrentqueue
Development files for moodycamel-concurrentqueue
This project links 4 native package records across 4 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
Project identity
- Project
- concurrentqueue
- Publisher
- Not authoritatively mapped
- Native package records
- 4
- Operating systems
- debian-12, debian-13, fedora-43, fedora-44
- License expression
- (BSD-2-Clause OR BSL-1.0) AND Zlib
- Metadata completeness
- 100/100 (not a software quality rating)
- Homepage
- Visit upstream site
- Source repository
- Open source repository
Source-reported description
The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.
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)
- libconcurrentqueue-dev1.0.3+ds-1
Debian 12 (Bookworm) / libdevel / source concurrentqueue
industrial-strength lock-free queue for C++
allbookworm
Debian 13 (Trixie)
- libconcurrentqueue-dev1.0.4+ds-2
Debian 13 (Trixie) / libdevel / source concurrentqueue
industrial-strength lock-free queue for C++
amd64arm64trixie
Fedora 43
- moodycamel-concurrentqueue-devel1.0.4-7.fc43
Fedora 43 / Unspecified / source moodycamel-concurrentqueue
Development files for moodycamel-concurrentqueue
noarch43
Fedora 44
- moodycamel-concurrentqueue-devel1.0.4-8.fc44
Fedora 44 / Unspecified / source moodycamel-concurrentqueue
Development files for moodycamel-concurrentqueue
noarch44
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.