Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

stb single-file public domain libraries for C/C++

License

NotificationsYou must be signed in to change notification settings

nothings/stb

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

single-file public domain (or MIT licensed) libraries for C/C++

This project discusses security-relevant bugs in public in Github Issues and Pull Requests, and it may take significant time for security fixes to be implemented or merged. If this poses an unreasonable risk to your project, do not use stb libraries.

Noteworthy:

Most libraries by stb, except: stb_dxt by Fabian "ryg" Giesen, original stb_image_resizeby Jorge L. "VinoBS" Rodriguez, and stb_image_resize2 and stb_sprintf by Jeff Roberts.

librarylastest versioncategoryLoCdescription
stb_vorbis.c1.22audio5584decode ogg vorbis files from file/memory to float/16-bit signed output
stb_hexwave.h0.5audio680audio waveform synthesizer
stb_image.h2.30graphics7988image loading/decoding from file/memory: JPG, PNG, TGA, BMP, PSD, GIF, HDR, PIC
stb_truetype.h1.26graphics5079parse, decode, and rasterize characters from truetype fonts
stb_image_write.h1.16graphics1724image writing to disk: PNG, TGA, BMP
stb_image_resize2.h2.13graphics10616resize images larger/smaller with good quality
stb_rect_pack.h1.01graphics623simple 2D rectangle packer with decent quality
stb_perlin.h0.5graphics428perlin's revised simplex noise w/ different seeds
stb_ds.h0.67utility1895typesafe dynamic array and hash tables for C, will compile in C++
stb_sprintf.h1.10utility1906fast sprintf, snprintf for C/C++
stb_textedit.h1.14user interface1429guts of a text editor for games etc implementing them from scratch
stb_voxel_render.h0.893D graphics3807Minecraft-esque voxel rendering "engine" with many more features
stb_dxt.h1.123D graphics719Fabian "ryg" Giesen's real-time DXT compressor
stb_easy_font.h1.13D graphics305quick-and-dirty easy-to-deploy bitmap font for printing frame rate, etc
stb_tilemap_editor.h0.42game dev4187embeddable tilemap editor
stb_herringbone_wa...0.7game dev1221herringbone Wang tile map generator
stb_c_lexer.h0.12parsing941simplify writing parsers for C-like languages
stb_divide.h0.94math433more useful 32-bit modulus e.g. "euclidean divide"
stb_connected_comp...0.96misc1049incrementally compute reachability on grids
stb_leakcheck.h0.6misc194quick-and-dirty malloc/free leak-checking
stb_include.h0.02misc295implement recursive #include support, particularly for GLSL

Total libraries: 21Total lines of C code: 51103

FAQ

What's the license?

These libraries are in the public domain. You can do anything youwant with them. You have no legal obligationto do anything else, although I appreciate attribution.

They are also licensed under the MIT open source license, if you have lawyerswho are unhappy with public domain. Every source file includes an explicitdual-license for you to choose from.

How do I use these libraries?

The idea behind single-header file libraries is that they're easy to distribute and deploybecause all the code is contained in a single file. By default, the .h files in here act astheir own header files, i.e. they declare the functions contained in the file but don'tactually result in any code getting compiled.

So in addition, you should selectexactly one C/C++ source file that actually instantiatesthe code, preferably a file you're not editing frequently. This file should define aspecific macro (this is documented per-library) to actually enable the function definitions.For example, to use stb_image, you should have exactly one C/C++ file that doesn'tinclude stb_image.h regularly, but instead does

#define STB_IMAGE_IMPLEMENTATION#include "stb_image.h"

The right macro to define is pointed out right at the top of each of these libraries.

Are there other single-file public-domain/open source libraries with minimal dependencies out there?

Yes.

If I wrap an stb library in a new library, does the new library have to be public domain/MIT?

No, because it's public domain you can freely relicense it to whatever license your newlibrary wants to be.

What's the deal with SSE support in GCC-based compilers?

stb_image will either use SSE2 (if you compile with -msse2) orwill not use any SIMD at all, rather than trying to detect theprocessor at runtime and handle it correctly. As I understand it,the approved path in GCC for runtime-detection requireyou to use multiple source files, one for each CPU configuration.Because stb_image is a header-file library that compiles in onlyone source file, there's no approved way to build both anSSE-enabled and a non-SSE-enabled variation.

While we've tried to work around it, we've had multiple issues overthe years due to specific versions of gcc breaking what we're doing,so we've given up on it. See#280and#410 for examples.

Some of these libraries seem redundant to existing open source libraries. Are they better somehow?

Generally they're only better in that they're easier to integrate,easier to use, and easier to release (single file; good API; noattribution requirement). They may be less featureful, slower,and/or use more memory. If you're already using an equivalentlibrary, there's probably no good reason to switch.

Can I link directly to the table of stb libraries?

You can usethis URL to link directly to that list.

Why do you list "lines of code"? It's a terrible metric.

Just to give you some idea of the internal complexity of the library,to help you manage your expectations, or to let you know what you'regetting into. While not all the libraries are written in the samestyle, they're certainly similar styles, and so comparisons betweenthe libraries are probably still meaningful.

Note though that the lines do include both the implementation, thepart that corresponds to a header file, and the documentation.

Why single-file headers?

Windows doesn't have standard directories where librarieslive. That makes deploying libraries in Windows a lot morepainful than open source developers on Unix-derivates generallyrealize. (It also makes library dependencies a lot worse in Windows.)

There's also a common problem in Windows where a library was builtagainst a different version of the runtime library, which causeslink conflicts and confusion. Shipping the libs as headers meansyou normally just compile them straight into your project withoutmaking libraries, thus sidestepping that problem.

Making them a single file makes it very easy to justdrop them into a project that needs them. (Of course you canstill put them in a proper shared library tree if you want.)

Why not two files, one a header and one an implementation?The difference between 10 files and 9 files is not a big deal,but the difference between 2 files and 1 file is a big deal.You don't need to zip or tar the files up, you don't have toremember to attachtwo files, etc.

Why "stb"? Is this something to do with Set-Top Boxes?

No, they are just the initials for my name, Sean T. Barrett.This was not chosen out of egomania, but as a moderately saneway of namespacing the filenames and source function names.

Will you add more image types to stb_image.h?

No. As stb_image use has grown, it has become more importantfor us to focus on security of the codebase. Adding new imageformats increases the amount of code we need to secure, so itis no longer worth adding new formats.

Do you have any advice on how to create my own single-file library?

Yes.https://github.com/nothings/stb/blob/master/docs/stb_howto.txt

Why public domain?

I prefer it over GPL, LGPL, BSD, zlib, etc. for many reasons.Some of them are listed here:https://github.com/nothings/stb/blob/master/docs/why_public_domain.md

Why C?

Primarily, because I use C, not C++. But it does also make it easierfor other people to use them from other languages.

Why not C99? stdint.h, declare-anywhere, etc.

I still use MSVC 6 (1998) as my IDE because it has better human factorsfor me than later versions of MSVC.

About

stb single-file public domain libraries for C/C++

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages


[8]ページ先頭

©2009-2025 Movatter.jp