The first directory in the Tools, Options, Directories list is
"$(VCInstallDir)bin" and sure enough, there is no cl.exe in that folder. I
did find a cl.exe in "$(VCInstallDir)bin\x86_amd64" but it seems to be a
64-bit compiler. My questions are: In a standard install is there supposed
to be a cl.exe in the "$(VCInstallDir)bin" directory? Where is the cl.exe
for 32-bit C++ compiles?
--
Scott McPhillips [VC++ MVP]
Scott:
My Vista is x64, and cl.exe is indeed in
C:\Program Files (x86)\Microsoft Visual Studio 9.0\vc\bin
And it works!
--
David Wilkinson
Visual C++ MVP
Scott:
(I sent this yesterday, but it does not seem to have found its way to the server.)
I run 2005 and 2008 interchangeably and even simultaneously and haven't had
any problems (with C++ that is). I'm having lots of problems with finding
.NET 3.5 web stuff, but that's a different issue.
Tom
"Scott McPhillips [MVP]" <org-dot-mvps-at-scottmcp> wrote in message
news:%23x%23kBH9C...@TK2MSFTNGP02.phx.gbl...
In your 2008 setup, is cl.exe in
"C:\Program Files\Microsoft Visual Studio 9.0\VC\bin"
?
I don't have a cl.exe there, and that causes an error.
If it is there, what is the size & date of the 32-bit cl.exe?
Thanks
"Scott McPhillips [MVP]" <org-dot-mvps-at-scottmcp> ha scritto nel messaggio
news:e4IhyPfD...@TK2MSFTNGP04.phx.gbl...
> In your 2008 setup, is cl.exe in
> "C:\Program Files\Microsoft Visual Studio 9.0\VC\bin"
> ?
> I don't have a cl.exe there, and that causes an error.
> If it is there, what is the size & date of the 32-bit cl.exe?
Mine is 122 KB big, and dated 2007 November 8th.
The MD5 hash is the following:
CFF9B41B7B5C89113E2C295AC38D1814
HTH,
Giovanni
I'm running VS 2008 Pro - 32-bit SP1; Vista Home Premium 32-bit, no SP1
and there is a cl.exe in
C:\Program Files\Microsoft Visual Studio 9.0\vc\bin.
cl.exe:
date: 7/30/2008 12:05pm
size: 127KB (size on disk: 129,520 bytes)
Frank
Victor
"Scott McPhillips [MVP]" <org-dot-mvps-at-scottmcp> wrote in message
news:e4IhyPfD...@TK2MSFTNGP04.phx.gbl...
Two things:
One, did you happen to install VS on a drive different than the OS Partition
drive? If so, a lot of times, some of it get's installed on the OS
partition drive and some of it gets installed on the drive you selected.
Two, are you running Vista x64? If so, then pay attention to Program Files
and Program Files (x86). It's quite likely cl.exe is under Program Files
(x86) if that is the case.
On a side note. I have VS 2005 and VS 2008 installed on the same box and
run them simultaneously without any issues.
Leo V.
"Scott McPhillips [MVP]" <org-dot-mvps-at-scottmcp> wrote in message
news:%23x%23kBH9C...@TK2MSFTNGP02.phx.gbl...
Thanks Leo, and the problem is not solved, but neither of those issues
applies in my case. It does seem as though it installed the 64 bit compiler
and not the 32-bit one, but it's on a 32-bit Vista machine.
Did you also install VB and C#? I did read somewhere that if those are not
selected then C++ doesn't install correctly. But I haven't tried that
option yet.
I reinstalled VS 2008 with VB, C# and C++ all selected and this time it
(C++) worked! The first two times I tried the install I had selected C++
only, and those installs failed to install the 32-bit C++ compiler cl.exe.
Scott:
Ya just never know when you might need that VB.NET...
Thank God for disk space.
At any rate, glad you got things going Scott. Your tips here are quite
helpful and I'd hate to think they would slow down if you couldn't get the
latest compiler up and running.
"David Wilkinson" <no-r...@effisols.com> wrote in message
news:u5$haIIIJ...@TK2MSFTNGP03.phx.gbl...
Thank You!
> Ya just never know when you might need that VB.NET...
(assuming "ya" == "you"...)
There is a particular scenario in which I think VB.NET is the best
programming tool available (better than C#): automation of Office
applications (Word, Excel, etc.).
In fact, automation of Office applications is based on COM and IDispatch,
and this is a scenario in which VB.NET's "late binding" feature comes in
handy.
You can read here an example comparing VB.NET use of late binding vs. C#
code based on reflection:
http://www.hanselman.com/blog/BackToBasicsVarDim.aspx
In that particular case, I do prefer VB.NET simplicity over C#
reflection-based boilerplate code.
As we say: choose the best tool for the particular job.
Giovanni