Enter the query into the form above. You can look for specific version of a package by using @ symbol like this: gcc@10.
API method:
GET /api/packages?search=hello&page=1&limit=20
where search is your query, page is a page number and limit is a number of items on a single page. Pagination information (such as a number of pages and etc) is returned
in response headers.
If you'd like to join our channel search send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
This package provides a complete Clang toolchain for C/C++ development to be installed in user profiles. This includes Clang, as well as libc (headers and binaries, plus debugging symbols in the debug output), and Binutils.
Clang is a compiler front end for the C, C++, Objective-C and Objective-C++ programming languages. It uses LLVM as its back end. The Clang project includes the Clang front end, the Clang static analyzer, and several code analysis tools.
LLD is a high-performance linker, built as a set of reusable components which highly leverage existing libraries in the larger LLVM Project.
ROCm device libraries provide AMD-specific device-side language runtime libraries, namely oclc, ocml, ockl, opencl, hip and hc.
LLVM is a compiler infrastructure designed for compile-time, link-time, runtime, and idle-time optimization of programs from arbitrary programming languages. It currently supports compilation of C and C++ programs, using front-ends derived from GCC 4.0.1. A new front-end for the C family of languages is in development. The compiler infrastructure includes mirror sets of programming tools as well as libraries with equivalent functionality.
rocMLIR is a MLIR-based convolution and GEMM kernel generator targetting AMD hardware.
This is a linker wrapper for LLD; like ld-wrapper, it wraps the linker to add any missing -rpath flags, and to detect any misuse of libraries outside of the store.
The "clang-runtime" library provides the implementations of run-time functions for C and C++ programs. It also provides header files that allow C and C++ source code to interface with the "sanitization" passes of the clang compiler. In LLVM this library is called "compiler-rt".
This package provides a bare-bones logging library for C++, with only a printf-like syntax and five logging levels.
MultiTail can monitor, color, filter, and merge log files and command output in multiple windows in a terminal.
Google glog is a library that implements application-level logging. This library provides logging APIs based on C++-style streams and various helper macros. You can log a message by simply streaming things to log at a particular severity level. It allows logging to be controlled from the command line.
Google glog is a library that implements application-level logging. This library provides logging APIs based on C++-style streams and various helper macros. You can log a message by simply streaming things to log at a particular severity level. It allows logging to be controlled from the command line.
Spdlog is a very fast header-only/compiled C++ logging library.
Plog is a C++ logging library that is designed to be simple, small and flexible. It is created as an alternative to existing large libraries and provides some unique features such as CSV log format and wide string support.
Rsyslog offers high-performance, great security features and a modular design. While it started as a regular syslogd, rsyslog has evolved into a kind of swiss army knife of logging, being able to accept inputs from a wide variety of sources, transform them, and output the results to diverse destinations.
Spdlog is a very fast header-only/compiled C++ logging library.
Log4cpp is library of C++ classes for flexible logging to files, syslog, IDSA and other destinations. It is modeled after the Log4j Java library, staying as close to their API as is reasonable.
The log4cxx packages provides a C++ logging framework patterned after Apache log4j which uses the Apache Portable Runtime for most platform-specific code.
QLogo is an interpreter for the Logo language written in C++ using Qt and OpenGL. Specifically, it mimics, as reasonably as possible, the UCBLogo interpreter.
The Lout document formatting system reads a high-level description of a document similar in style to LaTeX and produces a PostScript or plain text output file.
Lout offers an unprecedented range of advanced features, including optimal paragraph and page breaking, automatic hyphenation, PostScript EPS file inclusion and generation, equation formatting, tables, diagrams, rotation and scaling, sorted indexes, bibliographic databases, running headers and odd-even pages, automatic cross referencing, multilingual documents including hyphenation (most European languages are supported), formatting of computer programs, and much more, all ready to use. Furthermore, Lout is easily extended with definitions which are very much easier to write than troff of TeX macros because Lout is a high-level, purely functional language, the outcome of an eight-year research project that went back to the beginning.
Lsof stands for LiSt Open Files, and it does just that. It lists information about files that are open by the processes running on the system.
This library makes libuv available to Lua scripts.
LuaSocket is a Lua extension library that is composed by two parts: a C core that provides support for the TCP and UDP transport layers, and a set of Lua modules that add support for functionality commonly needed by applications that deal with the Internet.
Among the supported modules, the most commonly used implement the SMTP (sending e-mails), HTTP (WWW access) and FTP (uploading and downloading files) client protocols. These provide a very natural and generic interface to the functionality defined by each protocol. In addition, you will find that the MIME (common encodings), URL (anything you could possible want to do with one) and LTN12 (filters, sinks, sources and pumps) modules can be very handy.
This Lua module offers an interface to the GNU readline library.
The function readline() is a wrapper, which invokes the GNU readline, adds the line to the end of the history list, and then returns the line. Usually you call save_history() before the program exits, so that the history list is saved to the histfile.
This Lua module can dialogue with the user on the controlling-terminal of the process (typically /dev/tty) as returned by ctermid(). It also support most of readline's alternative interface, namely handler_install, read_char and handler_remove, and readline's custom completion.