SWCompression
A framework with (de)compression algorithms and functions for working with various archives and containers.
What is this?
SWCompression is a framework with a collection of functions for:
- Decompression (and sometimes compression) using different algorithms.
- Reading (and sometimes writing) archives of different formats.
- Reading (and sometimes writing) containers such as ZIP, TAR and 7-Zip.
It also works on Apple platforms, Linux, and Windows.
All features are listed in the tables below. “TBD” means that feature is planned but not implemented (yet).
|
Deflate |
BZip2 |
LZMA/LZMA2 |
LZ4 |
| Decompression |
✅ |
✅ |
✅ |
✅ |
| Compression |
✅ |
✅ |
TBD |
✅ |
|
Zlib |
GZip |
XZ |
ZIP |
TAR |
7-Zip |
| Read |
✅ |
✅ |
✅ |
✅ |
✅ |
✅ |
| Write |
✅ |
✅ |
TBD |
TBD |
✅ |
TBD |
Also, SWCompression is written with Swift only.
Installation
SWCompression can be integrated into your project using Swift Package Manager.
Note: SWCompression versions 4.8.6 and earlier were also made available via CocoaPods or Carthage.
To install with Swift Package manager, add SWCompression to you package dependencies and specify it as a dependency for
your target, e.g.:
import PackageDescription
let package = Package(
name: "PackageName",
dependencies: [
.package(name: "SWCompression", url: "https://github.com/tsolomko/SWCompression.git",
from: "4.9.0")
],
targets: [
.target(
name: "TargetName",
dependencies: ["SWCompression"]
)
]
)
More details you can find in Swift Package Manager’s Documentation.
Usage
Basic Example
For example, if you want to decompress “deflated” data just use:
// let data = <Your compressed data>
let decompressedData = try? Deflate.decompress(data: data)
However, it is unlikely that you will encounter deflated data outside of any archive. So, in the case of GZip archive
you should use:
let decompressedData = try? GzipArchive.unarchive(archive: data)
Handling Errors
Most SWCompression functions can throw errors and you are responsible for handling them. If you look at the list of
available error types and their cases, you may be frightened by their number. However, most of the cases (such as
XZError.wrongMagic) exist for diagnostic purposes.
Thus, you only need to handle the most common type of error for your archive/algorithm. For example:
do {
// let data = <Your compressed data>
let decompressedData = try XZArchive.unarchive(archive: data)
} catch let error as XZError {
// <handle XZ related error here>
} catch let error {
// <handle all other errors here>
}
Documentation
Every function or type of SWCompression’s public API is documented. This documentation can be found at its own
website or via a slightly shorter link:
swcompression.tsolomko.me
Sophisticated example
There is a small command-line program, “swcomp”, which is included in this repository in “Sources/swcomp”. It can be
built using Swift Package Manager (only available on macOS).
IMPORTANT: The “swcomp” command-line tool is NOT intended for general use.
Contributing
Whether you find a bug, have a suggestion, idea, feedback or something else, please
create an issue on GitHub. If you have any questions, you can ask
them on the Discussions page.
In the case of a bug, it will be especially helpful if you attach a file (archive, etc.) that caused the bug to occur.
If you’d like to contribute, please create a pull request on GitHub.
Executing tests locally
If you want to run tests on your computer, you need to do a couple of additional steps after cloning the repository:
git submodule update --init --recursive
cd "Tests/Test Files"
cp gitattributes-copy .gitattributes
git lfs pull
git lfs checkout
These commands will download the files used in tests which are stored in a
separate repository using Git LFS. There are two reasons for
this complicated setup. Firstly, some of these files can be quite big, and it would be unfortunate if the users of
SWCompression had to download them during the installation. Secondly, Swift Package Manager and contemporary versions of
Xcode don’t always work well with git-lfs-enabled repositories. To prevent any potential problems test files were moved
into another repository.
Please note, that if you want to add a new type of test files, in addition to running git lfs track, you have to
also copy into the “Tests/Test Files/gitattributes-copy” file a line this command adds to the “Tests/Test Files/.gitattributes”
file. Do not commit the “.gitattributes” file to the git history. It is git-ignored for a reason!
Please also be mindful of Git LFS bandwidth quota on GitHub: try to limit downloading lfs’d files using git lfs pull.
In CI we use some caching techniques to help with the quota, so if you’re going to add new tests that require several
new test files you should try to submit them all together to reduce the amount of times CI needs to recreate the cache
(recreating the cache requires to do git lfs pull for all test files).
Using whole module optimizations is recommended for the best performance. They are enabled by default in the Release build
configuration.
Tests Results document contains results of benchmarking of various functions.
Why?
First of all, existing solutions for working with compression, archives and containers have certain disadvantages. They
might not support a particular compression algorithm or archive format and they all have different APIs, which sometimes
can be slightly confusing for users, especially when you mix different libraries in one project. This project attempts to
provide missing (and sometimes existing) functionality through the unified API which is easy to use and remember.
Secondly, in some cases it may be important to have a compression framework written entirely in Swift, without relying
on either system libraries or solutions implemented in other languages. Additionaly, since SWCompression is written
completely in Swift without Objective-C, it can also be used on Linux, and Windows.
Future plans
- Performance…
- Better Deflate compression.
- Something else…
License
MIT licensed
References
评论