Threads support and WASMīy default, when the threads Cargo feature is enabled, this library uses multi-threading. as_slice() on it (to copy the pixels), or use. If you get an error that From> is not implemented, then either don't pass by reference (moves, avoids copying), or call. new_image() can now take ownership of its argument to avoid copying. The openmp Cargo feature has been renamed to threads. Please fix any deprecation warnings you may get, because the deprecated functions will be removed. The imagequant v4 is almost entirely backwards-compatible, with small changes that the Rust compiler will point out (e.g. If you've used the imagequant-sys crate, switch to the higher-level imagequant crate. The shared libimagequant library exports only a stable ABI for C programs, and this interface is not useful for Rust programs. It uses this library as a Cargo dependency via its Rust-native interface. However, pngquant v4 does not support unbundling.
Pngquant v2 can use this library as a dynamic library. No runtime deps (apart from Cargo-internal ones). This makes Rust 1.60 and cargo-c package a build-time dependency.
IMAGEOPTIM. HOW TO
The cargo-c tool knows how to build and link so/dylib properly, and generates an accurate pkg-config file, so it's de-facto required for a correct system-wide install of a dynamic library.Ĭargo cinstall -prefix=/usr/local -destdir=. I wish there was a more standard and lightweight solution than using the cargo-c tool, so if you're good at wrangling linker flags and symbol visibility, please send pull requests. I hoped I could build a dynamic library just by wrapping the static library, but apparently that won't work, so I can't easily recreate the old make install. Building with makeĬonfigure & make is gone. If you want to build a dynamic library, but aren't bothered by soname and rpath being wrong, modify imagequant-sys/Cargo.toml and add "cdylib" to the existing crate-type property, and then cargo build -release will do its usual half-finished job and build target/release/libimagequant. See Cargo docs for things like cargo fetch or cargo vendor (but I don't recommend vendoring). If you want to set up off-line builds or override dependencies, it works the same as for every other Rust project. This library is now a typical Rust/Cargo library. It has the same sover, so it can be a drop-in replacement for the previous C version. The API and ABI of this library remains the same. If you're an application developer, please use the static linking option above - that option is much easier, and gives smaller executables. C dynamic library for package maintainers Same for cross-compiling to other platforms. If you're building for Android, run rustup target add aarch64-linux-android cargo build -release -target aarch64-linux-android and use target/aarch64-linux-android/release/libimagequant_sys.a. If you're building for macOS or iOS, see included xcodeproj file (add it as a subproject to yours). The API, ABI, and header files remain the same, so everything else should work the same. It produces target/release/libimagequant_sys.a static library. To build the library, install Rust via rustup, and run: C static library usersįiles for C/C++ are now in the imagequant-sys/ subdirectory, not in the root of the repo. If you do not want to upgrade, you can keep using the C version of the library in the 2.x branch of the repo. You will need to install Rust 1.60+ to build it, and adjust your build commands. libimagequant v4 is written entirely in Rust, but still exports the same C interface for C programs. Feel free to ask for details and custom licensing terms if you need them. For use in closed-source software, AppStore distribution, and other non-GPL uses, you can obtain a commercial license.
IMAGEOPTIM. SOFTWARE
For Free/Libre Open Source Software it's available under GPL v3 or later with additional copyright notices for historical reasons.The app works efficiently, it’s brain-dead simple to use, and it does just what it promises.See docs.rs for the library API documentation. While I wish ImageOptim included a running total of just how much smaller all the files in a given batch are combined, that’s at worst a minor oversight. That number can vary widely depending upon your source image, but I’ve compressed some images more than 80-percent. ImageOptim doesn’t offer a whole lot of insight into what it’s doing, but you can mouse-over an individual image on the list to see which tool the app is using to shrink the image.Īlongside each filename, ImageOptim lists its file size (in bytes), and the percentage by which the file size was shrunk from the original.
The app immediately starts optimizing the images, using one or more of a slew of command-line image optimization tools:
IMAGEOPTIM. PLUS
Drag images onto its window or Dock icon, or click on the plus (+) button to select images from a standard Open dialog box. ImageOptim’s interface is Spartan but functional.
0 kommentar(er)
