print compilation options

[Bonj]

Is there any way to get VS to print the compilation settings that it is
invoking as it is calling all the compiler tools, for instance
instead of

Compiling...
stdafx.cpp
myprog.cpp
Linking...

I want
cl.exe ...blah blah blah...
link.exe ...blah blah blah...

so I know what options it is using, in order to find out how it builds a
damn static library!
If I try compiling with /D"_LIB", it complains that entry point must be
defined, and tries to create an .exe. If I use /LDd, then it outputs a .LIB
file - fine, but it outputs a DLL aswell, and it's the DLL where the
functions are! I want ALL the functions to be in the .lib file, not just
their stubs. But I want to do this without using Visual Studio.
If a combination of cl.exe and link.exe can't create a static library, then
how the bloody hell does Visual Studio do it????!!!


Why don't I use Visual Studio you might ask? Well however immoral nicking it
is, to nick it for the purposes of building an application that I intend to
sell is something that I would be a bit hypocritical if I did - especially
when the application I'm building is to help other people build *their*
applications. So I'm sticking to the SDK.
Please DON'T say why don't I use the Express edition - answer, because it
can't create resource files which my application needs (and someone at
Microsoft has confirmed this to be an issue that isn't likely to be fixed, as
the resource editor relies on ATL in some way).

[Carl Daniel [VC++ MVP]]

Bonj wrote:

Is there any way to get VS to print the compilation settings that it
is invoking as it is calling all the compiler tools,

Just look at the buildlog.htm after a build from within VS - it tells you
everything you need to know.

-cd

[Bonj]

Right, OK.
It confirms that the build process uses "lib.exe". Can anybody confirm for
sure whether this is or isn't included in the 32-bit SDK, or is it something
you can *only* get if you purchase Visual Studio, and if the latter, any
thoughts on why, other than sheer bloody-mindedness?

Also, any thoughts on whether gcc or borland includes a lib.exe (or
equivalent)?
I'm rapidly losing patience with this microsoft shite, they give us
optimizing compiler and then take away a whole bunch of other stuff...

"Carl Daniel [VC++ MVP]" wrote:

Bonj wrote:

Is there any way to get VS to print the compilation settings that it
is invoking as it is calling all the compiler tools,

Just look at the buildlog.htm after a build from within VS - it tells you
everything you need to know.

-cd

[Mike Labosh]

>> Is there any way to get VS to print the compilation settings that it

is invoking as it is calling all the compiler tools,

Just look at the buildlog.htm after a build from within VS - it tells you
everything you need to know.

Interesting. How do you get it to generate that? Is that a VC++ only
feature? I would love to get that for VB / C#!
--
Peace & happy computing,

Mike Labosh, MCSD
"I have no choice but to believe in free will."

[Carl Daniel [VC++ MVP]]

Bonj wrote:

Right, OK.
It confirms that the build process uses "lib.exe". Can anybody
confirm for sure whether this is or isn't included in the 32-bit SDK,
or is it something you can *only* get if you purchase Visual Studio,
and if the latter, any thoughts on why, other than sheer
bloody-mindedness?
I'm sure lib.exe is included in the PSDK tools. Even if it's not, it's just
a wrapper on link.exe anway. Trying typing

link /lib

on a command prompt...
Also, any thoughts on whether gcc or borland includes a lib.exe (or
equivalent)?

They certainly do.

-cd

[Carl Daniel [VC++ MVP]]

Mike Labosh wrote:

Is there any way to get VS to print the compilation settings that it
is invoking as it is calling all the compiler tools,

Just look at the buildlog.htm after a build from within VS - it
tells you everything you need to know.

Interesting. How do you get it to generate that? Is that a VC++ only
feature? I would love to get that for VB / C#!

It's a C++ feature, AFIAK.

-cd