Mercurial > pidgin

view libpurple/win32/libpurplerc.rc.in @ 30467:3d045343e04d

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Use some fully qualified dll locations. There wasn't anything wrong with this as far as I can tell, but since we know specifically where what we're looking for is, this is probably better. Also, plug a small leak and try to find our enchant dll instead of any other one that is in the PATH.
author Daniel Atallah <daniel.atallah@gmail.com>
date Tue, 31 Aug 2010 01:49:53 +0000
parents dd3c5b3dd3e0
children
line wrap: on
line source

#include <winver.h>
#include "version.h"

VS_VERSION_INFO VERSIONINFO
  FILEVERSION PURPLE_MAJOR_VERSION,PURPLE_MINOR_VERSION,PURPLE_MICRO_VERSION,0
  PRODUCTVERSION PURPLE_MAJOR_VERSION,PURPLE_MINOR_VERSION,PURPLE_MICRO_VERSION,0
  FILEFLAGSMASK 0
  FILEFLAGS 0
  FILEOS VOS__WINDOWS32
  FILETYPE VFT_DLL
  FILESUBTYPE VFT2_UNKNOWN
  BEGIN
    BLOCK "StringFileInfo"
    BEGIN
      BLOCK "040904B0"
      BEGIN
        VALUE "CompanyName", "The Pidgin developer community"
        VALUE "FileDescription", "LibPurple Library"
        VALUE "FileVersion", "@PURPLE_VERSION@"
        VALUE "InternalName", "libpurple"
        VALUE "LegalCopyright", "Copyright (C) 1998-2010 The Pidgin developer community (See the COPYRIGHT file in the source distribution)."
        VALUE "OriginalFilename", "libpurple.dll"
        VALUE "ProductName", "LibPurple"
        VALUE "ProductVersion", "@PURPLE_VERSION@"
      END
    END
    BLOCK "VarFileInfo"
    BEGIN
      VALUE "Translation", 0x409, 1200
    END
  END