Boost logo

Boost-Build :

From: (b84037_at_[hidden])
Date: 2004-07-01 21:27:11

> >
> > It
> What do you mean by "it"?
Humm... maybe my expression was wrong. Please forget it.

> Well, the change was made because a user wanted to run msvc setup
> before invoking resource compiler. Do you think it's not reasonable

Mmmm... I think if it is possible to imply using another toolset
while initializing the toolset. So we just declare using the 'main'
toolset as usual.

using msvc : 6.0 ; <== .rc support
using msvc : 7.1 ; <== .rc support
using free_msvc : 7.1 ; <== no .rc support

> > So that I could compile .rc
> > files
> > by invoking 'windres.exe' and 'res2coff.exe' while I
use 'Microsoft
> > Visual C++ Toolkit 2003' toolset.
> I believe you can just pass "windres" as the name of resource
compiler when
> configuring msvc. Can you try this?
I tried it... but the following error message appeared.
..\..\out\common\images\Win32\msvc-7.1\release\images_res.obj : fatal
error LNK1000: Internal error during Pass1
I compile images.rc to images.res by using windres.
Rename images.res to images.obj, and then include it in source list.
rebuild again, it works! So the .o object format (COFF?) produced
by 'windres.exe' is not accepted by 'link.exe'.
But I use 'objdump' to extract the information of object. Compare to
the one produced by 'cvtres.exe'...Both of them are all pe-i386
I have no idea what is the different.
Is anybody familiar with the object format?
Maybe somebody can find out what happens.

-- PAL


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at