https://github.com/chromium/mini_chromium

A small collection of useful low-level (“base”) routines from Chromium
https://github.com/chromium/mini_chromium

Last synced: about 2 months ago
JSON representation

A small collection of useful low-level (“base”) routines from Chromium

• Host: GitHub
• URL: https://github.com/chromium/mini_chromium
• Owner: chromium
• License: bsd-3-clause
• Created: 2017-05-04T19:20:57.000Z (over 7 years ago)
• Default Branch: main
• Last Pushed: 2024-08-22T02:22:39.000Z (3 months ago)
• Last Synced: 2024-09-25T19:35:24.212Z (about 2 months ago)
• Language: C++
• Homepage: https://chromium.googlesource.com/chromium/mini_chromium
• Size: 712 KB
• Stars: 250
• Watchers: 16
• Forks: 69
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE
  • Authors: AUTHORS

Awesome Lists containing this project

README

        


# mini_chromium

This is mini_chromium, a small collection of useful low-level (“base”) routines

from the [Chromium open-source project](https://dev.chromium.org/Home). Chromium

is large, sprawling, full of dependencies, and a web browser. mini_chromium is

small, self-contained, and a library. mini_chromium is especially useful as a

dependency of other code that wishes to use Chromium’s base routines. By using

mini_chromium, other projects’ code can function in a standalone environment

outside of Chromium without having to treat all of Chromium as a dependency.

When building as part of Chromium, those projects’ code can use Chromium’s own

(non-mini_chromium) base implementation.

Code provided in mini_chromium provides the same interface as the equivalent

code in Chromium.

While it’s a goal of mini_chromium to maintain interface compatibility with

Chromium’s base library for the interfaces it does implement, there’s no

requirement that it use the same implementations as Chromium’s base library.

Many of the implementations used in mini_chromium are identical to Chromium’s,

but many others have been modified to eliminate dependencies that are not

desired in mini_chromium, and a few are completely distinct from Chromium’s

altogether. Additionally, when mini_chromium provides an interface in the form

of a file or class present in Chromium, it’s not bound to provide all functions,

methods, or types that the Chromium equivalent does. The differences noted above

notwithstanding, the interfaces exposed by mini_chromium’s base are and must

remain a strict subset of Chromium’s.

[Crashpad](https://crashpad.chromium.org/) is the chief consumer of

mini_chromium.

Mark Mentovai


[email protected]