All submissions to this site are governed by the Second Life Viewer Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.

Review Board 1.6.11

Welcome to the Second Life Viewer Code Review tool.
See the documentation on our wiki for how to use this site.

VWR-24347 Reversion in Copy3rdPartyLibs.cmake -- cannot find msvc* files using VS 2005 Express

Review Request #68 - Created Dec. 29, 2010 and submitted

Jonathan Yap Reviewers
2.5 viewer
vwr-24347
None viewer-development
Environment: Windows, VS 2005 Express

Back in the days of v2.1 I was able to supply the following option to develop.py, which would allow me to specify the location of
msvcr80.dll
msvcp80.dll
Microsoft.VC80.CRT.manifest

-DMSVC_REDIST_PATH:PATH=E:/some/path

There was a similar code path for the debug files
-DMSVC_DEBUG_REDIST_PATH=E:/some/path

This files cannot be found by the Express compiler so without a way of telling the compiler where to find them they have to be dropped into the build tree manually.

At some point Copy3rdPartyLibs.cmake was rewritten and this option was dropped.
I tried using -DMSVC_REDIST_PATH:PATH=E:/some/path with my VS 2005 Express compiler and obtained the desired result. 

I don't have the debug files to test -DMSVC_DEBUG_REDIST_PATH=E:/some/path
Posted (Jan. 3, 2011, 3:24 p.m.)
Could you identify in the log history of the file when that "at some point" happened? There might be a reason for it though I can't imagine one off the top of my head.
Posted (Jan. 4, 2011, 4:14 p.m.)
Those lines have been missing since a long time: the first version in hg is already missing them:
https://bitbucket.org/lindenlab/viewer-development/changeset/07304583316d
  1. They are not in that early version, but they are (plus code for VS2008) in a V2.1 copy I have of that file, but at some point were taken out again.
Posted (Jan. 17, 2011, 7:33 a.m.)
Given that we are in the process of moving to VS2010, I suggest that this is not worth doing
  1. Oz, I think it is worth doing, but doing it it a more general and forward-looking way, unless VS2010 Express will not have this issue. Please see the comment I just wrote in https://jira.secondlife.com/browse/vwr-24347 and let me know what you think.
Ship it!
Posted (Jan. 20, 2011, 11:30 p.m.)
Though we'll be moving to VS 2010, this patch will help some folks in the community.