Talk:Viewer 2 Microsoft Windows Builds

Development tool notes

• UniCode NSIS
  • This is the package installer used to build Setup.exe.

Mailing list discussions on compile errors, and more

For completeness's sake, there are threads on the mailing list on a few errors found during compilation:

• Not being able to find objidl.h in the Microsoft Windows SDK, when compiling llwindow: https://lists.secondlife.com/pipermail/opensource-dev/2011-April/006562.html

  Can be caused by path problems or some installation conflicts with the DirectX SDK.

• stdint.h typedef conflicts between Quicktime and VS2010: https://lists.secondlife.com/pipermail/opensource-dev/2011-April/006565.html

  Can be solved by some small edits to header files to make sure the two don't bash on each other.

I also ended up with bad variables in the CMake cache (some probably related to the above) and I needed to edit build-vc100\CMakeCache.txt. They including DUSE_KDU, DINPUT_LIBRARY, DIRECTX_INCLUDE_DIR, DIRECTX_LIBRARY_DIR, and DXGUID_LIBRARY. Celierra Darling 14:41, 22 April 2011 (PDT)

Moving this here since it looks like they changed some things to address this so that autobuild configure will download the right things:

• If Cmake/Autobuild attempts to download FMOD and can't, one can turn off FMOD by adding two dashes (--), and then the extra configuration option -DFMOD:BOOL=FALSE. Similarly, if it attempts to download KDU and can't, try adding -DINSTALL_PROPRIETARY:BOOL=FALSE -DUSE_KDU:BOOL=FALSE after those dashes.

  For example, autobuild configure -- -DFMOD:BOOL=FALSE -DINSTALL_PROPRIETARY:BOOL=FALSE -DUSE_KDU:BOOL=FALSE

I'm also moving this comment from the "Iteratively fix things until the compile succeeds" section since it looks like it's been there since the first revision of the page without resolution: ((TBD - add any fixup steps here. e.g. does fmod375.dll need to be moved into RelWithDbgInfo at this step?))

Celierra Darling 15:02, 22 April 2011 (PDT)