WINDRES(1)

📦 version 2.47, in arch rolling

💅 WINDRES 💅

ok so bestie, welcome to windres — the GNU Development Tools girlie who manipulates Windows resources ✨ like she literally reads resources from an input file and copies them into an output file, no cap. it's giving "glow-up for your .rc files" and honestly? iconic.

✨ SYNOPSIS ✨

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

🦋 DESCRIPTION 🦋

okay so real talk: windres reads resources from an input file and copies them into an output file. and either one of those files can be in one of three formats, periodt:

  • rc — a text format read by the Resource Compiler. very "I write my resources by hand" main character energy 🎀
  • res — a binary format generated by the Resource Compiler. mysterious. binary. slay.
  • coff — a COFF object or executable. the final form fr fr.

the exact description of these different formats is available in documentation from Microsoft — like, go ask Redmond, bestie, she has the lore 📚

when windres converts from the rc format to the res format, it is acting like the Windows Resource Compiler. she's cosplaying! and when windres converts from the res format to the coff format, it is acting like the Windows CVTRES program. versatile queen 👑

when windres generates an rc file, the output is similar but not identical to the format expected for the input. 🙈 and when an input rc file refers to an external filename, an output rc file will instead include the file contents. so it just... absorbs the file. ate and left no crumbs.

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. she's intuitive like that 💅 so:

  • 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. lowkey the most casual flex ever.

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 vibe. that's the pipeline. iykyk.

🌸 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. and if there are no non-option arguments, then windres will read from standard input. ⚠️ but heads up bestie: windres can not read a COFF file from standard input. that's a no.
  • -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 compatibility with rc the option -fo is also accepted, but its use is not recommended. it's giving deprecated-but-still-invited-to-the-party 💀
  • -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. same guessing energy, different direction 💫
  • -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. first place = default, she's predictable like that 👑
  • --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. the default preprocessor is gcc. 🧚
  • --preprocessor-arg option — when windres reads an rc file, it runs it through the C preprocessor first. this option may be used to specify additional text to be passed to preprocessor on its command line. this option can be used multiple times to add multiple options to the preprocessor command line. 🔁 if the --preprocessor option has not been specified then a default set of preprocessor arguments will be used, with any --preprocessor-arg options being placed after them on the command line. these default arguments are -E, -xc-header and -DRC_INVOKED. memorise those, bestie 💖
  • -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. 🗂️ now the messy part: 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, simple prefix it with ./ to disable the backward compatibility. crisis averted 🫡
  • -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. undefine her, she's over it 🙅‍♀️
  • -r — ignored for compatibility with rc. literally just vibing in the options list, doing nothing, still invited 🫥
  • -v — enable verbose mode. this tells you what the preprocessor is if you didn't specify one. she's nosy and we love that 🔍
  • -c val, --codepage val — specify the default codepage to use when reading an rc file. val should be a hexadecimal prefixed by 0x or decimal codepage code. the valid range is from zero up to 0xffff, but the validity of the codepage is host and configuration dependent. ⚠️ so like, in range ≠ guaranteed valid, girly. it depends on your host and config 🌈
  • -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, but make it cute ✨
  • --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). 😭 retro Windows trauma, we remember
  • --no-use-temp-file — use popen, not a temporary file, to read the output of the preprocessor. this is the default behaviour. the standard girlie 💅
  • -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. only if she was built that way, bestie — otherwise this option is just knocking on a locked door 🚪
  • @file — read command-line options from file. the options read are inserted in place of the original @file option. if file does not exist, or cannot be read, then the option will be treated literally, and not removed. 🤯

options in file are separated by whitespace. a whitespace character may be included in an option by surrounding the entire option in either single or double quotes. any character (including a backslash) may be included by prefixing the character to be included with a backslash. the file may itself contain additional @file options; any such options will be processed recursively. it's files all the way down 🌀

👀 SEE ALSO 👀

  • the Info entries for binutils. go read her, she's the source 🫶

copyright (c) 1991-2026 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.3 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 was binutils-2.47, dated 2026-08-26 — shoutout to the footer girlies, mwah 💋 periodt. 🌈👑

📦 where this page comes from