Annoying problem with header files
From: Bonj (a_at_b.com)
Date: 12/19/04
- Next message: Antony: "tracewpp event tracing macros example"
- Previous message: John: "problem with GetCommState()"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 19 Dec 2004 16:22:13 -0000
I have encountered a really strange problem with header files, that I've had
before. I can't remember what the resolution was, if indeed there was one.
Basically I went through what I would describe as a 'flurry' of installing
various different SDKs in the hope that one of them would include the ml.exe
tool. I had previously gone through a similar flurry trying to find one that
would contain a midl.exe that would process ADO correctly. However at the
end of the second flurry (which consisted of more uninstalls than installs)
there was a load of header files missing from the include directory,
including windows.h, from the remaining SDK.
Now, I have reinstalled windows on a brand new hard disk and any of the SDKs
I try to install complete successfully, but don't install all the header
files necessary. There are lots missing, including windows.h. It typically
has about 30 or 40 header files in the include folder, the real number
should be into 4 figures.
I have gone to the 'sdkupdate' site on the MS website and gone for the XP
SP2 full SDK (the one that requires an ActiveX control) and downloaded the
'full' SDK installer for that - it is only about a megabyte but takes ages
to install (it is now doing so) so must be in the process of downloading the
required components selectively.
Looking at the folder structure it has already created it does, thank god,
seem to have installed about 1,000 .h files including windows.h. However, it
doesn't seem to have installed the cl.exe in its bin directory. Its bin
directory is populated with lots of other exes such as oleview.exe and
tb20.exe. Whether it is going to install the compiler I don't know but it
seems unlikely.
The mystery now seems to be why do not all the SDKs install the complete
set of windows header files, especially the essential ones such as
windows.h.
The ones I tried that have failed include:
.NET 2005 Beta SDK
Visual C++ Toolkit 2003
Full .NET 1.1 SDK
I don't know what is wrong, but I can only presume that the installer does
actually contain the files (I can't see why it wouldn't since when I posted
about this previously, other people reported the installers working
successfully), but is looking in the registry or somewhere else, and
deducing that I have already got another SDK installed and therefore
presumes that it has got no new header files that I need, when this is not
actually the case. That doesn't explain why it would do that on a fresh
windows installation though. Anybody else suffered this?
Can anybody shed any light on this if they have any more idea than me what
is going on. Or aswell, if anybody has any idea how I can extract the files
from the SDK's setup.exe forcibly and do the install more manually.
And if anybody could shed any light on whether the "XP SP2 SDK" from the
sdkupdate site (http://www.microsoft.com/msdownload/platformsdk/sdkupdate)
is supposed to include the compiler, and if not, what else should I install
in order to get it, and whatever else I do install will it duplicate
anything or conflict with it?
Also, is there not a "non-.NET" SDK still going that I can dowload from MS
that includes C/C++ compiler and tools (and preferably windows.h) but
doesn't require .NET framework, or is the "XP SP2 SDK" just that?
- Next message: Antony: "tracewpp event tracing macros example"
- Previous message: John: "problem with GetCommState()"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
