Where is rc.exe

For RC, you would need to specify 0xaa11 0xbb Navigation menu Personal tools Log in. Namespaces Page Discussion. Views Read View source View history. RAD Studio Assistance Recent changes. This page was last edited on 11 September , at It also explains that the linker automatically converts the. If you also look at. Res Files as Linker Input , it mentions that the linker uses the cvtres utility to convert the.

This is in the same directory as the linker, but you can run it yourself if you don't want to rely on the linker. If you do run it without input, it still displays a help and one of the options is the machine, and I would imagine that when the linker runs cvtres, it will use the same machine that it detects or is passed into link. The tools have to be this level of platform independent because of how the toolset works. For the cross compilers, some tools aren't duplicated cvtres is one of them.

So for an xx64 cross compile, it will be running the x86 version. For an xx86 cross compile it will run the x64 version. I'm using the compiler via the it's assembly and start the compilation process from inside my own build-tool. But when I compile an x86 project, I get this rc. When I copy the x64 rc. But chaning the "executable path" of the project doesn't help, because then all tools will be executed in the x64 version and that's not compatible I don't think Microsoft is interested in fixing this If you set the.

So while I didn't add anything useful, all I know for sure is that when you use MSBuild directly, or through Visual Studio, if you set it to use the x64 tools then even with the xx86 cross compile it will use the 64 bit version of rc.

Visual Studio team doesn't support things being in fixed locations. Running vsdevcmd. Workaround is to use the VsDevCmd. GitHub Windows Server Azure Devops Windows Server Skip to content. Star 4. New issue. Jump to bottom.

Labels OS: Windows. OS: Windows. Linked pull requests. Copy link. Tool information Tool name: Resource Compiler Add or update?