WINDRES(1)

💖 WINDRES(1) — the GNU Development Tools girlies' guide 💖

okay bestie, so this is the manual for windres, one of the GNU Development Tools, and I'm gonna walk you through it like we're texting at 2am 🫶

---

✨ NAME ✨

windres — manipulate Windows resources. that's it, that's the whole vibe. 💅

---

🌸 SYNOPSIS 🌸

windres [options] [input-file] [output-file]

like. options, then maybe an input, then maybe an output. she's flexible. 👑

---

🦋 DESCRIPTION 🦋

so windres reads resources from an input file and copies them into an output file. that's the core plotline. 💖

either file may be in one of three formats:

• rc — a text format read by the Resource Compiler. words! letters! human-readable! ✨
• res — a binary format generated by the Resource Compiler. crunchy. 🍓
• coff — a COFF object or executable.

the exact description of these different formats lives in documentation from Microsoft. (not us. go ask them. 💀)

when windres converts from the rc format to the res format, she's acting like the Windows Resource Compiler. iconic behaviour. and when windres converts from the res format to the coff format, she's acting like the Windows CVTRES program. she contains multitudes. 🌈

when windres generates an rc file, the output is similar but not identical to the format expected for the input. not a copy-paste situation, bestie. specifically: when an input rc file refers to an external filename, an output rc file will instead include the file contents. she inlines it. no cap.

if the input or output format is not specified, windres will guess based on the file name, or, for the input file, the file contents. the guessing rules, periodt:

• a file with an extension of .rc will be treated as an rc file
• a file with an extension of .res will be treated as a res file
• a file with an extension of .o or .exe will be treated as a coff file

if no output file is specified, windres will print the resources in rc format to standard output. surprise drop!! ✨

the normal use is for you to write an rc file, use windres to convert it to a COFF object file, and then link the COFF file into your application. this will make the resources described in the rc file available to Windows. that's the whole pipeline, and it eats every single time. 🔥

---

🎀 OPTIONS 🎀

• -i filename, --input filename — the name of the input file. if this option is not used, then windres will use the first non-option argument as the input file name. if there are no non-option arguments, then windres will read from standard input. > ⚠️ heads up: windres can not read a COFF file from standard input. sorry bestie, that door is locked. 🙈
• -o filename, --output filename — the name of the output file. if this option is not used, then windres will use the first non-option argument, after any used for the input file name, as the output file name. if there is no non-option argument, then windres will write to standard output. > ⚠️ windres can not write a COFF file to standard output either. also: note, for compatability with rc the option -fo is also accepted, but its use is not recommended. legacy behaviour, we don't stan. 💅
• -J format, --input-format format — the input format to read. format may be res, rc, or coff. if no input format is specified, windres will guess, as described above. ✨
• -O format, --output-format format — the output format to generate. format may be res, rc, or coff. if no output format is specified, windres will guess, as described above. ✨
• -F target, --target target — specify the BFD format to use for a COFF file as input or output. this is a BFD target name; you can use the --help option to see a list of supported targets. normally windres will use the default format, which is the first one listed by the --help option. 👑
• --preprocessor program — when windres reads an rc file, it runs it through the C preprocessor first. this option may be used to specify the preprocessor to use, including any leading arguments. the default preprocessor argument is gcc -E -xc-header -DRC_INVOKED. yes that whole string. she's long but she's correct. 💖
• -I directory, --include-dir directory — specify an include directory to use when reading an rc file. windres will pass this to the preprocessor as an -I option. windres will also search this directory when looking for files named in the rc file. > ⚠️ if the argument passed to this command matches any of the supported formats (as described in the -J option), it will issue a deprecation warning, and behave just like the -J option. new programs should not use this behaviour. if a directory happens to match a format, simply prefix it with ./ to disable the backward compatibility. iykyk. 🫶
• -D target, --define sym[=val] — specify a -D option to pass to the preprocessor when reading an rc file.
• -U target, --undefine sym — specify a -U option to pass to the preprocessor when reading an rc file.
• -r — ignored for compatibility with rc. she's just here for the vibes. literally does nothing. 💀
• -v — enable verbose mode. this tells you what the preprocessor is if you didn't specify one. she'll spill the tea on herself. 🌸
• -l val, --language val — specify the default language to use when reading an rc file. val should be a hexadecimal language code. the low eight bits are the language, and the high eight bits are the sublanguage. bit math, bestie. 🧚
• --use-temp-file — use a temporary file to instead of using popen to read the output of the preprocessor. use this option if the popen implementation is buggy on the host (eg., certain non-English language versions of Windows 95 and Windows 98 are known to have buggy popen where the output will instead go the console). > ⚠️ yes, actual old-Windows bug lore. she's seen things. 😭
• --no-use-temp-file — use popen, not a temporary file, to read the output of the preprocessor. this is the default behaviour. ✨
• -h, --help — prints a usage summary.
• -V, --version — prints the version number for windres.
• --yydebug — if windres is compiled with YYDEBUG defined as 1, this will turn on parser debugging. very niche, very slay. 🔥

---

🌈 SEE ALSO 🌈

• the Info entries for binutils.

---

👑 COPYRIGHT 👑

Copyright (c) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled ``GNU Free Documentation License''.

---

and that's the whole page, bestie 🫶 this one came from binutils-2.15.97, dated 2005-04-20 — go forth and compile your resources, you absolute main character 💅✨