Author Topic: windres.exe: no resources  (Read 4702 times)

walkeraj

  • Guest
windres.exe: no resources
« on: October 12, 2007, 01:08:45 am »
Silly windres...

Error I'm getting is the famous: "windres.exe: no resources"

I'm attempting to compile allegro from source, and the dllver.rc it ships with is throwing this error with Code::Blocks.  Windres doesn't exactly give the most descriptive error messages (even calling it without arguments gives "no resources"), and I can't see the commandline commands code::blocks is using to attempt to build this, so I'm at a standstill.  The contents of dllver.rc are pretty simple:

Code
#include <windows.h>


1 VERSIONINFO
FILEVERSION 4, 2, 2, 0
PRODUCTVERSION 4, 2, 2, 0
FILEOS VOS__WINDOWS32
FILETYPE VFT_DLL
BEGIN
   BLOCK "StringFileInfo"
   BEGIN
      BLOCK "040904E4"
      BEGIN
         VALUE "Comments", "Please see AUTHORS for a list of contributors\000"
         VALUE "CompanyName", "Allegro Developers\000\000"
         VALUE "FileDescription", "Allegro\000"
         VALUE "FileVersion", "4.2.2\000"
         VALUE "InternalName", "ALLEG42\000"
         VALUE "LegalCopyright", "Copyright © 1994-2007 Allegro Developers\000\000"
         VALUE "OriginalFilename", "ALLEG42.DLL\000"
         VALUE "ProductName", "Allegro\000"
         VALUE "ProductVersion", "4.2.2\000"
      END
   END

   BLOCK "VarFileInfo"
   BEGIN
      VALUE "Translation", 0x0809, 1252
   END
END

So I'm imagining it's not seeing the file properly or something...  is this file supposed to be compiled last? If so, that could be the problem, as it seems to be attempting to build it midway through, before it finishes the dll.  All paths have been adjusted and whatnot.  Also, is there any way to view the commandline output for code::blocks so that I can attempt to diagnose such problems myself?

Thanks in advance for your help!

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7591
    • My Best Post
Re: windres.exe: no resources
« Reply #1 on: October 12, 2007, 01:43:38 am »
Try this
Compiling: Settings -> Compiler and Debugger -> Tab "Other" -> Compiler logging = "Full command line".

Tim S
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org