Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building NVDA for 64 bit fails on Windows 7 32 bit, MSVC 2010 #2508

Closed
nvaccessAuto opened this issue Jul 5, 2012 · 6 comments

Comments

Projects
None yet
2 participants
@nvaccessAuto
Copy link

commented Jul 5, 2012

Reported by mherrmann.at on 2012-07-05 16:11
I'm having trouble building the 64 bit version of the current development version of NVDA. My system is:

  • Windows 7 Professional SP 1 32 bit
  • Visual Studio 2010 Professional.

Building for 32 bit works fine:

scons dist targetArchitectures=x86

When I just do

scons dist

then I get an error dialog saying "The program can't start because mspdb100.dll is missing from your computer. Try reinstalling the program to fix this problem.". Calling vcvarsall using the command
call "c:\Program Files\Microsoft Visual Studio 10.0\VC\vcvarsall.bat"
gets rid of this error dialog, however results in a lot of unresolved externals (see attached file "unresolved externals.txt").

All problems go away when I comment out the following the following lines in site_scons\site_tools\windowsSdk.py:

    ...
    #msvc.msvc_setup_env_once=lambda env: False
    #msvc.msvc_exists=lambda: True
    ...
    #env['MSVC_USE_SCRIPT']=False
    ...

This change is in the attached file "windowsSdk_fixed.patch".

Should I switch to a different version of Visual Studio? I failed to find any documentation on the recommended Visual Studio version.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented Jul 5, 2012

Attachment unresolved externals.txt added by mherrmann.at on 2012-07-05 16:11
Description:

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented Jul 5, 2012

Attachment windowsSdk_fixed.patch added by mherrmann.at on 2012-07-05 16:12
Description:

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented Jul 5, 2012

Comment 1 by mdcurran on 2012-07-05 23:04
We only officially support Windows SDK 7.0 and 7.1. Windows SDK comes with all compilers and tools needed.
There may be conflicts trying to use both Windows SDK and VS.
I understand this is not a great situation, but it does work okay for the majority building NVDA.
Scons's support for Windows SDK 7.1 is currently broken hense the need for our custom windowsSDK scons tool. If the problem gets fixed in scons then we can remove this tool and perhaps VS may work again, though I'm not sure.
Leaving this ticket open as it crtainly would be nice to improve this situation at some point.
Changes:
Milestone changed from None to near-term

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented Jul 6, 2012

Comment 3 by mherrmann.at on 2012-07-06 09:13
I see. I uninstalled VS and all Windows SDKs, then re-installed Windows SDK 7.1 and everything works now. Thank you.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented Oct 17, 2012

Comment 4 by nvdakor on 2012-10-17 17:54
I think we may need to put this into source readme - to NOT install compilers shipping with SDK 7.0 if they already have VS2008 or 2010 installed on their systems.

@nvaccessAuto nvaccessAuto added this to the near-term milestone Nov 10, 2015

@jcsteh jcsteh added the invalid label Jun 23, 2016

@jcsteh

This comment has been minimized.

Copy link
Contributor

commented Jun 23, 2016

No longer relevant, as we now only support Visual Studio 2015 and there's no longer a separate SDK tool chain.

@jcsteh jcsteh closed this Jun 23, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.