[Winmerge-svn] SF.net SVN: winmerge: [5215] branches/R2_8/Docs/Developers
Windows visual diff and merge for files and directories
Brought to you by:
christianlist,
grimmdp
From: <ki...@us...> - 2008-03-29 10:20:14
|
Revision: 5215 http://winmerge.svn.sourceforge.net/winmerge/?rev=5215&view=rev Author: kimmov Date: 2008-03-29 03:20:12 -0700 (Sat, 29 Mar 2008) Log Message: ----------- PATCH: [ 1928278 ] Docs: Move ShellExt building to compile doc Modified Paths: -------------- branches/R2_8/Docs/Developers/Compiling.html branches/R2_8/Docs/Developers/readme-developers.html Modified: branches/R2_8/Docs/Developers/Compiling.html =================================================================== --- branches/R2_8/Docs/Developers/Compiling.html 2008-03-29 10:18:42 UTC (rev 5214) +++ branches/R2_8/Docs/Developers/Compiling.html 2008-03-29 10:20:12 UTC (rev 5215) @@ -63,8 +63,8 @@ <li><a href="#Compiling_scew">Compiling SCEW</a></li> <li><a href="#Compiling_pcre">Compiling PCRE</a></li> <li><a href="#Compiling_core">Compiling WinMerge executables</a></li> + <li><a href="#ShellExt64">Shell Extension (64-bit)</a></li> <li><a href="#VS2005">Visual Studio 2005</a></li> - <li><a href="#ShellExt">Shell Extension</a></li> </ol> @@ -236,6 +236,47 @@ <li>Plugin dlls : Unicode Release MinDependency</li> </ul> +<h3><a name="ShellExt64">Shell Extension (64-bit)</a></h3> +<p>This is a bit tricky, and needs some patience to setup.</p> + +<h4>Needed tools</h4> +<ul> + <li>Visual Studio 2003 or later (Might work for earlier, but I haven't tried it)</li> + <li>Platform SDK (for Windows 2003 SP1) with at least following components installed: + <ul> + <li>Configuration Options</li> + <li>Microsoft Windows Core SDK <strong>with tools and build environments</strong></li> + <li>Microsoft Web Workshop (IE) SDK</li> + <li>Microsoft Data Access Services (MDAC) SDK <i>not sure about this</i></li> + </ul> + </li> +</ul> + +<h4>Starting Visual Studio and opening the project</h4> +<p>We need to start Visual Studio from Platform SDK's 64-bit environment so that we get all +needed environment variables and paths correctly set. So:</p> +<ol> + <li>Start 64-bit Platform SDK environment:<br> + From Start menu: Platform SDK --> Open Build Environment Window --> Windows XP/2003 64-bit + environment --> Release/Debug environment</li> + <li>CD to Visual Studio install folder/Common7/IDE</li> + <li>Start Visual Studio with command:<br> + <code>devenv /USEENV (uses open environment)</code></li> + <li>Open <code>ShellExtensionX64.vcproj</code> from <code>ShellExtension</code> project + folder.</li> +</ol> + +<p>Make sure you have 64-bit target selected in Project Settings. Then check that paths are OK. +You <strong>MUST</strong> build to separate directory than 32-bit targets so that files don't +mix up.</p> + +<p>Compiling should now succeed. If not, check that all needed PSDK components are installed +and that paths are OK. If you are compiling in 32-bit Windows you get error about registering +but that is expected to happen.</p> + +<p>64-bit ShellExtension is registered to 64-bit Windows just like counterparts in 32-bit world:<br> +<code>regsvr ShellExtensionX64.dll</code></p> + <h3><a name="VS2005">Visual Studio 2005</a></h3> <p>When the VC6 project file (.dsp) is converted to a Visual Studio 2005 project, it does not compile correctly as is. The problem is Visual Studio 2005 automatically generates and Modified: branches/R2_8/Docs/Developers/readme-developers.html =================================================================== --- branches/R2_8/Docs/Developers/readme-developers.html 2008-03-29 10:18:42 UTC (rev 5214) +++ branches/R2_8/Docs/Developers/readme-developers.html 2008-03-29 10:20:12 UTC (rev 5215) @@ -441,45 +441,5 @@ path of <code>WinMerge.exe</code> you mainly use as its value. If this value exists ShellExtension does not care about another path value.</p> -<h4>Compiling for 64-bit Windows</h4> -<p>This is a bit tricky, and needs some patience to setup.</p> - -<h5>Needed tools</h5> -<ul> - <li>Visual Studio 2003 or later (Might work for earlier, but I haven't tried it)</li> - <li>Platform SDK (for Windows 2003 SP1) with at least following components installed: - <ul> - <li>Configuration Options</li> - <li>Microsoft Windows Core SDK <strong>with tools and build environments</strong></li> - <li>Microsoft Web Workshop (IE) SDK</li> - <li>Microsoft Data Access Services (MDAC) SDK <i>not sure about this</i></li> - </ul> - </li> -</ul> - -<h5>Starting Visual Studio and opening the project</h5> -<p>We need to start Visual Studio from Platform SDK's 64-bit environment so that we get all -needed environment variables and paths correctly set. So:</p> -<ol> - <li>Start 64-bit Platform SDK environment:<br> - From Start menu: Platform SDK --> Open Build Environment Window --> Windows XP/2003 64-bit - environment --> Release/Debug environment</li> - <li>CD to Visual Studio install folder/Common7/IDE</li> - <li>Start Visual Studio with command:<br> - <code>devenv /USEENV (uses open environment)</code></li> - <li>Open <code>ShellExtensionX64.vcproj</code> from <code>ShellExtension</code> project - folder.</li> -</ol> - -<p>Make sure you have 64-bit target selected in Project Settings. Then check that paths are OK. -You <strong>MUST</strong> build to separate directory than 32-bit targets so that files don't -mix up.</p> - -<p>Compiling should now succeed. If not, check that all needed PSDK components are installed -and that paths are OK. If you are compiling in 32-bit Windows you get error about registering -but that is expected to happen.</p> - -<p>64-bit ShellExtension is registered to 64-bit Windows just like counterparts in 32-bit world:<br> -<code>regsvr ShellExtensionX64.dll</code></p> </body> </html> \ No newline at end of file This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |