yyc12345/stb
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

expand explanation of why single file

Browse Source
This commit is contained in:
Sean Barrett 2015-04-14 03:13:45 -07:00
parent 3db3e56696
commit 977cce8cc7
2 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@ -63,12 +63,21 @@ live. That makes deploying libraries in Windows a lot more
painful than open source developers on Unix-derivates generally painful than open source developers on Unix-derivates generally
realize. (It also makes library dependencies a lot worse in Windows.) realize. (It also makes library dependencies a lot worse in Windows.)
There's also a common problem in Windows where a library was built
against a different version of the runtime library, which causes
link conflicts and confusion. Shipping the libs as headers means
you normally just compile them straight into your project without
making libraries, thus sidestepping that problem.
Making them a single file makes it very easy to just Making them a single file makes it very easy to just
drop them into a project that needs them. (Of course you can drop them into a project that needs them. (Of course you can
still put them in a proper shared library tree if you want.) still 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, 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. 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 to
remember to attach *two* files, etc.
#### Why "stb"? Is this something to do with Set-Top Boxes? #### Why "stb"? Is this something to do with Set-Top Boxes?

9
tools/README.footer.md
View File

@ -38,12 +38,21 @@ live. That makes deploying libraries in Windows a lot more
painful than open source developers on Unix-derivates generally painful than open source developers on Unix-derivates generally
realize. (It also makes library dependencies a lot worse in Windows.) realize. (It also makes library dependencies a lot worse in Windows.)
There's also a common problem in Windows where a library was built
against a different version of the runtime library, which causes
link conflicts and confusion. Shipping the libs as headers means
you normally just compile them straight into your project without
making libraries, thus sidestepping that problem.
Making them a single file makes it very easy to just Making them a single file makes it very easy to just
drop them into a project that needs them. (Of course you can drop them into a project that needs them. (Of course you can
still put them in a proper shared library tree if you want.) still 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, 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. 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 to
remember to attach *two* files, etc.
#### Why "stb"? Is this something to do with Set-Top Boxes? #### Why "stb"? Is this something to do with Set-Top Boxes?