Build the client with MSVC 2008 - Revision history

Cjkelly1: VS2008 instructions are not needed. I will be requesting deletion of this page.

2019-10-26T23:35:06Z

VS2008 instructions are not needed. I will be requesting deletion of this page.

2019-10-26T09:27:22Z

Changed referenced PR. The previous PR was created incorrectly, and is now invalid.

2019-06-17T17:43:12Z

Add the UruDocProject header and category footer tags

2019-04-06T18:51:00Z

fix typos and add project edit

2019-04-06T18:15:06Z

change fftwrap.c link

2019-04-06T17:40:00Z

fix typo. compiled tools are copied into "tools" directory, not "test"

2019-04-06T08:34:58Z

2019-04-06T08:33:05Z

2019-04-06T08:31:33Z

Specify that these instructions were developed with MSVC 2008 SP1 Express.

2019-04-06T08:29:42Z

@@ Line 7: / Line 7: @@
 Please note that the client created using these instructions has not undergone extensive testing.<BR>
-These instructions need the project files from [https://bitbucket.org/OpenUru_org/cwe-ou/pull-requests/45 Pull request #45] on the CWE bitbucket.
+These instructions need the project files from [https://bitbucket.org/OpenUru_org/cwe-ou/pull-requests/48 Pull request #48] on the CWE bitbucket.
 == Items needed to compile ==

@@ Line 1: / Line 1: @@
 == Introduction ==
 This document provides steps to build the CWE client with MSVC 2008 SP1 Express, with minimal changes from the current CWE-OU source as of 05-Dec-2018 [https://foundry.openuru.org/hg/CWE-ou/file/d991af4b4960].<BR>
@@ Line 359: / Line 361: @@
 Change all linker references of "dxerr9.lib" to "dxerr.lib"
 </li>

@@ Line 133: / Line 133: @@
 <ol style="list-style-type:lower-latin">
 <li> Create a directory and extract the Speex 1.2.0 archive into it.</li>
-<li> Unfortunately, the speex-1.2.0 release is missing the "fftwrap.c" file.  Obtain the missing file from the Speex github repository and copy it into "speex-1.2.0\libspeex" directory (the directory that also has "fftwrap.h" in it).  [https://github.com/xiph/speex/blob/master/libspeex/fftwrap.c fftwrap.c]</li>
+<li> Unfortunately, the speex-1.2.0 release is missing the "fftwrap.c" file.  Obtain the missing file from the Speex github repository and copy it into "speex-1.2.0\libspeex" directory (the directory that also has "fftwrap.h" in it).  [https://raw.githubusercontent.com/xiph/speex/master/libspeex/fftwrap.c fftwrap.c]</li>
 <li> Open "\speex-1.2.0\win32\VS2008\libspeex.sln" in the VS2008 IDE.  Ignore "project missing" errors - we are only building libspeex. </li>
 <li> Click on configuration drop-down on the upper left and select "Release_RTL_dll" </li>

@@ Line 331: / Line 331: @@
 If, after building the client, you require the server prep tools (plFileSecure, plFileEncrypt, plPythonPak), right click on those specific projects and click "Build".<BR>
-The compiled files will be copied into the "CWE\MOULOpenSourceClientPlugin\Plasma20\test" directory.
+The compiled files will be copied into the "CWE\MOULOpenSourceClientPlugin\Plasma20\tools" directory.
 == DirectX notes ==

@@ Line 26: / Line 26: @@
 * All release version libraries are compiled as "Multi-threaded DLL (/MD)"
 * All debug version libraries are compiled as "Multi-threaded Debug DLL (/MDd)"
-* It is understood that the specified DirectX SDK (Aug 2007) has expired messages for one of it's components.  We are using that DirectX SDK version because it is the newest available SDK that does not require source changes to use.  The earlier October 2005 version is no longer available from Microsoft.
+* It is understood that the specified DirectX SDK (Aug 2007) has expired messages for one of it's components.  The client does not use that particular component, and we are using that DirectX SDK version because it is the newest available SDK that does not require source changes to use.  The earlier October 2005 version is no longer available from Microsoft.
 <BR>
 * Crypto keys are located in "CWE\MOULOpenSourceClientPlugin\Plasma20\Sources\Plasma\NucleusLib\pnNetBase".  Edit the *.hpp files with a text editor to replace Cyan's keys with your own server's keys.  Always clean your solution and rebuild when you change crypto keys, to make sure they are updated.<BR>

@@ Line 32: / Line 32: @@
 * Server hostnames, IP addresses, and ports are located in the following files:
 <u>The status URL:  </u><BR>
-"CWE\MOULOpenSourceClientPlugin/Plasma20/Sources/Plasma/Apps/plClient/winmain.cpp"
+"CWE\MOULOpenSourceClientPlugin/Plasma20/Sources/Plasma/Apps/plClient/winmain.cpp"<BR>
 "CWE\MOULOpenSourceClientPlugin/Plasma20/Sources/Plasma/Apps/plUruLauncher/Main.cpp"<BR><BR>
 <u>The auth/gatekeeper address</u><BR>

@@ Line 335: / Line 335: @@
 == DirectX notes ==
-It is possible to use the [https://www.microsoft.com/en-us/download/details.aspx?id=6812 latest DirectX 9.0c SDK (June 2010)] with some more source changes.  This has not been tested either, but this basic documentation is here in case Microsoft decides to pull the link for the DX Aug 2007 SDK. <BR>
+It is possible to use the [https://www.microsoft.com/en-us/download/details.aspx?id=6812 latest DirectX 9.0c SDK (June 2010)] with some more source changes.  The client compiles and runs with these changes, but it has not been extensively tested.  This basic documentation is here in case Microsoft decides to pull the link for the DX Aug 2007 SDK. <BR>
 <li> In file "\CWE\MOULOpenSourceClientPlugin\Plasma20\Sources\Plasma\PubUtilLib\plPipeline\plDXPipeline.cpp"<BR>