Well, it's so long since I used the MS tools, I can't comment in detail
on how they work... I'll try and describe what I do with the mingw
tools, with reference to the sudoku example. I think the steps are
broadly analogous for both toolchains...

> Thanks, I am learning from the soduku example. I am having a 
> chicken egg issue with the order of the resource compiler and 
> linker. Is it the linker that is supposed to get the ouput of 
> the resource compiler to build the executable?

The "resource compiler" is just that, it takes in some source file(s),
and generates a .o file, that is then passed to the linker...

In the sudoku example, the source files are "sudoku.rc", which
references "sudoku.ico", and "sudokurc.h" which allows the other sources
to refer to the compiled resource.
So that's the 3 files you need.

At build time, "sudoku.rc" is compiled into "sudoku.o" and then passed
to the linker like any other object file.

Perhaps one of the MS tool users can contribute with some notes on what
the actual steps are in that toolchain.
It is possible, I suppose, that the recent (VC8 etc.) MS toolchains
store the icon info in the manifest file in some way, much like OSX does
in it's bundle files...??? I really don't know. If so, the "old way"
still works just fine, as I have code the works fine on vista built with
my old tools...





SELEX Sensors and Airborne Systems Limited
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL
A company registered in England & Wales.  Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************