A simple library to facilitate adding Resources (metainformation and icons) to Portable Executables (Windows executables and dynamic libraries).
Note: tauri-winres
is a fork of winres which no longer works on Rust 1.61 or higher and has been left unmaintained.
Before we begin you need to have the appropriate tools installed.
rc.exe
from the Windows SDKwindres.exe
andar.exe
from minGW64
If you are using Rust with the MSVC ABI you will need the Windows SDK for the GNU ABI you'll need minGW64.
Windows SDK can be found in the registry, minGW64 has to be in the path.
First, you will need to add a build script to your crate (build.rs
) by adding it to your crate's Cargo.toml
file:
[package]
#...
build = "build.rs"
[build-dependencies]
tauri-winres = "0.1"
Next, you have to write a build script. A short example is shown below.
// build.rs
fn main() {
if std::env::var("CARGO_CFG_TARGET_OS").unwrap() == "windows" {
let mut res = tauri_winres::WindowsResource::new();
res.set_icon("test.ico");
res.compile().unwrap();
}
}
That's it. The file test.ico
should be located in the same directory as build.rs
. Metainformation (like program version and description) is taken from Cargo.toml
's [package]
section.
Note that support for using this crate on non windows platforms is experimental. It is recommended to only use tauri-winres
on Windows hosts, by using cfg
as a directive to avoid building tauri-winres
on unix platforms alltogether.
[package]
#...
build = "build.rs"
[target.'cfg(windows)'.build-dependencies]
tauri-winres = "0.1"
Next, you have to write a build script. A short example is shown below.
// build.rs
#[cfg(windows)]
fn main() {
let mut res = tauri_winres::WindowsResource::new();
res.set_icon("test.ico");
res.compile().unwrap();
}
#[cfg(unix)]
fn main() {}
For added convenience, tauri-winres
parses Cargo.toml
for a package.metadata.tauri-winres
section:
[package.metadata.tauri-winres]
OriginalFilename = "PROGRAM.EXE"
LegalCopyright = "Copyright © 2016"
#...
This section may contain arbitrary string key-value pairs, to be included in the version info section of the executable/library file.
The following keys have special meanings and will be shown in the file properties of the Windows Explorer:
FileDescription
, ProductName
, ProductVersion
, OriginalFilename
and LegalCopyright
See MSDN for more details on the version info section of executables/libraries.
The original author and maintainers use this crate for their personal projects and although is has been tested in that context, we have no idea if the behaviour is the same everywhere.
To be brief, we are very much reliant on your bug reports and feature suggestions to make this crate better.