Difference between revisions of "Talk:Viewer 2 Microsoft Windows Builds"
Jonathan Yap (talk | contribs) (Added Guidelines section) |
Jonathan Yap (talk | contribs) |
||
| Line 2: | Line 2: | ||
=== A few style guidelines === | === A few style guidelines === | ||
The person who is following these instructions for the first time may know little or nothing about VS2010. Steps should be kept simple and explained in well written English, not in a succinct description that an experienced person would be able to follow. | *The person who is following these instructions for the first time may know little or nothing about VS2010. Steps should be kept simple and explained in well written English, not in a succinct description that an experienced person would be able to follow. | ||
If there is more than one way to do something only describe one of those ways. The philosophy at the start of this wiki page says, in part: to keep it brief, this page should only include steps we KNOW ARE NEEDED, not random hints. | *If there is more than one way to do something only describe one of those ways. The philosophy at the start of this wiki page says, in part: to keep it brief, this page should only include steps we KNOW ARE NEEDED, not random hints. | ||
A path to, or a menu entry, should be in '''bold'''. | *A path to, or a menu entry, should be in '''bold'''. | ||
A field you can change should be <code>highlighted</code>. | *A field you can change should be <code>highlighted</code>. | ||
Instructions should apply to Visual Studio Express. If there is a small difference between Express and Pro assume the Pro user is experienced and can figure it out. Try to avoid instructions such as "If Express do this" or "If Pro do this". | *Instructions should apply to Visual Studio Express. If there is a small difference between Express and Pro assume the Pro user is experienced and can figure it out. Try to avoid instructions such as "If Express do this" or "If Pro do this". | ||
These instructions were written collaboratively and tested by the authors for correctness in all four combinations of XP/Windows 7 and Express/Pro. If you are going to make a change to these instructions it is strongly suggested you make sure your change works for all these combinations. As your development environment may not be this extensive you may want to recruit help from people in the #opensl IRC channel who are using other OS and compiler configurations. | *These instructions were written collaboratively and tested by the authors for correctness in all four combinations of XP/Windows 7 and Express/Pro. If you are going to make a change to these instructions it is strongly suggested you make sure your change works for all these combinations. As your development environment may not be this extensive you may want to recruit help from people in the #opensl IRC channel who are using other OS and compiler configurations. | ||
Also before making a change make sure it is not an issue with your local environment. Check with others to see if they are also having this issue. | *Also before making a change make sure it is not an issue with your local environment. Check with others to see if they are also having this issue. | ||
=== Eliminate annoying IDE popup === | === Eliminate annoying IDE popup === | ||
Revision as of 05:18, 22 June 2012
Mailing list discussions on compile errors, and more
A few style guidelines
- The person who is following these instructions for the first time may know little or nothing about VS2010. Steps should be kept simple and explained in well written English, not in a succinct description that an experienced person would be able to follow.
- If there is more than one way to do something only describe one of those ways. The philosophy at the start of this wiki page says, in part: to keep it brief, this page should only include steps we KNOW ARE NEEDED, not random hints.
- A path to, or a menu entry, should be in bold.
- A field you can change should be
highlighted.
- Instructions should apply to Visual Studio Express. If there is a small difference between Express and Pro assume the Pro user is experienced and can figure it out. Try to avoid instructions such as "If Express do this" or "If Pro do this".
- These instructions were written collaboratively and tested by the authors for correctness in all four combinations of XP/Windows 7 and Express/Pro. If you are going to make a change to these instructions it is strongly suggested you make sure your change works for all these combinations. As your development environment may not be this extensive you may want to recruit help from people in the #opensl IRC channel who are using other OS and compiler configurations.
- Also before making a change make sure it is not an issue with your local environment. Check with others to see if they are also having this issue.
Eliminate annoying IDE popup
If you are compiling with the IDE and keep getting a popup along the lines of "improve microsoft visual studio performance" Either
- To hide on XP or 2003 Server, right-click on the Task Bar | Select Properties | Select Taskbar tab | select Hide inactive icons | Click Customize | Set the Behavior for item "Improve Microsoft Visual Studio" to "Always hide".
Or
- Follow the registry edit instructions just before "Was this information helpful?" at this link http://support.microsoft.com/kb/981741
Note: This second method did not work for me.
Jonathan Yap 8:43, 31 May 2011 (PDT)
Order of installing
I got errors during the installation of the directX SDK. the problems occured while it was installing the c++ Runtimes (which have already been installed before). So here is what i did to fix this:
- remove all 2010 installations
- install the DirectX SDK (June 2010) (that also installs the redistributable packages)
- Install the Visual C++ 2010 Express
- Install Windows SDK for Windows 7 and .NET Framework 4
- Run Microsoft Update
Gaia Clary 21:28, 8 Feb 2012 (CEST)
C2220 + C4819 in non-English environment
When you see the message like this:
error C2220: warning treated as error - no 'object' file generated warning C4819: The file contains a character that cannot be represented in the current code page (932)
(The message depends on the language you use.)
The cause is that the compiler fails when it try to treat BOM in some characters. Currently, the header files from COLLADA dom have several type of such characters. You need to dig in Drive:\your_path\build-vc100\packages\include\collada\1.4\dom and change all of them to avoid these errors.
Character Should be ” " “ " – - ‘ ' ’ '
If your editor has grep-and-replace feature, you can easily do that. Or, you can use sed, awk or other command line tool as well. In Cygwin or shell kin, cd to the header files directory above and run:
for FILE in *.h; do cp $FILE $FILE.bak; sed -e "s/[”“]/\"/g;s/–/-/g;s/[‘’]/'/g" $FILE.bak > $FILE; done
-- Mako 07:48, 11 June 2012 (PDT)
Missing msvcp100.dll/msvcr100.dll
Probably when you use Windows7 and VS2010, you may encounter some error message complaining about lacking msvcp100.dll or msvcr100.dll. It seems to have been solved in STORM-1150, but still has problem (maybe because of the double backslash (\\) in result). You will need to do manually copy missing dlls from C:\Windows\System32 to Drive:\your_path\build-vc100\sharedlibs\Release.
-- Mako 07:48, 11 June 2012 (PDT)
Please post "Style Guideline" here
To help people who are difficult to on the IRC but interested in this article. -- Mako 05:44, 22 June 2012 (PDT)