I tried to put version info in a resource script. rcc didn't squawk, but OPTLINK didn't like it.

---------------------8< output from smake >8---------------------
rcc -D__NT__ app4
link -NOI protowin.obj basewin.obj  winmain.obj app4win.obj
app4about.obj,app4.exe,,gdi32.lib,app4.def,app4.res

OPTLINK (R) for Win32  Release 7.50B1
Copyright (C) Digital Mars 1989 - 2001  All Rights Reserved

OPTLINK : Error 152: Cannot yet convert VERSION resources from 16 to
32-bit
------------------------8< snip >8------------------------

Is there a way to get version info in a Win32 executable?
 ../frank

On Mon, 03 Feb 2003 14:34:12 -0600, Frank Albe wrote:
> I tried to put version info in a resource script. rcc didn't squawk, but OPTLINK didn't like it.
> 
> ---------------------8< output from smake >8---------------------
> rcc -D__NT__ app4

Use "rcc -32 -D__NT__ app4" instead to generate a 32-bit resource file.


bye, Christof

-- 
http://cmeerw.org                                 JID: cmeerw@jabber.at mailto cmeerw at web.de

...and what have you contributed to the Net?

It worked. Thank you. I shouldn't have missed that switch. I was converting a little project from BCB5 and had been fighting it too long. It's good to know (this morning after RTFM) when using -32, "-D__NT__" isn't required.

On Mon, 3 Feb 2003 22:02:41 +0000 (UTC), Christof Meerwald
<cmeerw@web.de> wrote:

>On Mon, 03 Feb 2003 14:34:12 -0600, Frank Albe wrote:
>> I tried to put version info in a resource script. rcc didn't squawk, but OPTLINK didn't like it.
>> 
>> ---------------------8< output from smake >8---------------------
>> rcc -D__NT__ app4
>
>Use "rcc -32 -D__NT__ app4" instead to generate a 32-bit resource file.
>
>
>bye, Christof

 ../frank