CODEWITHSUNDEEP
c++boost
ibrabeicker
ibrabeicker

Reputation: 1839

Building Boost - can't find windows.h

I'm trying to build boost on windows 7 64-bits. Running bootstrap gives

execnt.c(29) : fatal error C1083: Cannot open include file: 'windows.h': No such file or directory

and some others. I have visual studio 9.0 and the places where I have windows.h is in

I have the SDK installed and even fully reinstalled Visual studio. Any way I can fix this?

Upvotes: 2

Views: 9349

Answers (3)

jack
jack

Reputation: 1

Edit %VS90COMNTOOLS%vsvars32.bat with administrator privileges any way you like, eg.

runas /user:Administrator "notepad %VS90COMNTOOLS%vsvars32.bat"

Find the section

:GetWindowsSdkDirHelper
@for /F "tokens=1,2*" %%i in ('reg query "%1\SOFTWARE\Microsoft\Microsoft SDKs\Windows" /v "CurrentInstallFolder"') DO (
    if "%%i"=="CurrentInstallFolder" (

Change it to

:GetWindowsSdkDirHelper
@for /F "tokens=1,2*" %%i in ('reg query "%1\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v6.0a" /v "InstallationFolder"') DO (
    if "%%i"=="InstallationFolder" (

When you install a newer version of the Windows SDK, it updates HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\CurrentInstallFolder to point to the newer version.

Unfortunately, the batch file that Visual Studio 2008 uses to set its paths uses this registry key to identify the location of the Windows SDK, so instead of pointing at the version of the Windows SDK that works with VS2008 (6.0a), it points to the the latest version to be installed.

Editing the registry is one option. A better option is to change the batch file so that it gets the right path from the registry, as above.

Upvotes: 0

ibrabeicker
ibrabeicker

Reputation: 1839

For future reference of anyone looking for the same error

I have installed visual studio without registry edition permission, so I had none of the environment variables set, those that boost libraries / libxml2 et al look for when calling the cl compiler

Giving myself permission to edit the registry and uninstalling/reinstalling all visual studio related programs solved it

Upvotes: 2

Edward Strange
Edward Strange

Reputation: 40859

Try running the boost build from a VS console rather than trying to run 'cmd'. It's probably somewhere in the start menu entry for VS (used to be anyway). It used to also be available from VS itself under tools, but I think they removed it there.

This version is just cmd, but it runs a batch script that sets a bunch of very important environment variables.

Upvotes: 5

Related Questions