[Winmerge-svn] SF.net SVN: winmerge: [5208] branches/R2_8/Docs
Windows visual diff and merge for files and directories
Brought to you by:
christianlist,
grimmdp
Menu
▾
▴
[Winmerge-svn] SF.net SVN: winmerge: [5208] branches/R2_8/Docs
|
From: <ki...@us...> - 2008-03-28 14:56:13
|
Revision: 5208
http://winmerge.svn.sourceforge.net/winmerge/?rev=5208&view=rev
Author: kimmov
Date: 2008-03-28 07:56:03 -0700 (Fri, 28 Mar 2008)
Log Message:
-----------
PATCH: [ 1927502 ] Docs: Create separate compiling doc
Modified Paths:
--------------
branches/R2_8/Docs/Developers/index.html
branches/R2_8/Docs/Developers/readme-developers.html
branches/R2_8/Docs/Users/ChangeLog.txt
branches/R2_8/Docs/index.html
Added Paths:
-----------
branches/R2_8/Docs/Developers/Compiling.html
Copied: branches/R2_8/Docs/Developers/Compiling.html (from rev 5207, trunk/Docs/Developers/Compiling.html)
===================================================================
--- branches/R2_8/Docs/Developers/Compiling.html (rev 0)
+++ branches/R2_8/Docs/Developers/Compiling.html 2008-03-28 14:56:03 UTC (rev 5208)
@@ -0,0 +1,254 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+ "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+ <title>Compiling.html</title>
+ <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
+ <style type="text/css">
+ <!--
+ body {
+ font-family: Verdana,Helvetica,Arial,sans-serif;
+ font-size: small;
+ }
+ code,pre {
+ font-family: "Courier New",Courier,monospace;
+ font-size: 1em;
+ }
+ h3 {
+ padding: 2px;
+ border-left: 4px solid #FFCC00;
+ border-bottom: 1px solid #FFCC00;
+ }
+ h4 {
+ padding: 2px;
+ border-left: 8px solid #FF9933;
+ border-bottom: 1px solid #FF9933;
+ }
+ h5 {
+ font-size: small;
+ }
+ pre {
+ margin-left: 25px;
+ margin-right: 25px;
+ padding: 5px;
+ background-color: #EEEEEE;
+ border: 1px solid black;
+ }
+ p.note {
+ padding: 5px;
+ background-color: #DDDDFF;
+ border: 1px solid blue;
+ }
+ acronym {
+ cursor: help;
+ border-bottom: 1px dotted black;
+ }
+ -->
+ </style>
+</head>
+<body>
+<h2>Compiling WinMerge</h2>
+
+<p>Compiling sources is usually the first thing you want to do. Source packages
+for different versions are available from SourceForge.net downloads or from
+Subversion repository. See <a href="readme-Subversion.html">readme-Subversion.html
+</a> for more information about Subversion repository and using it.</p>
+
+<h3>Table of Contents</h3>
+<ol>
+ <li><a href="#Environment">Environment</a></li>
+ <li><a href="#Buildall_bat">BuildAll.bat</a></li>
+ <li><a href="#ProjectFiles">Project Files</a></li>
+ <li><a href="#Compiling_expat">Compiling expat</a></li>
+ <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="#VS2005">Visual Studio 2005</a></li>
+ <li><a href="#ShellExt">Shell Extension</a></li>
+</ol>
+
+
+<h3><a name="Environment">Environment</a></h3>
+<h4>Supported Compilers</h4>
+<ul>
+ <li>Visual Studio 2003.Net + Service Pack 1 (used for releases)</li>
+ <li>Visual Studio 6 + Service Pack 6</li>
+ <li>Visual Studio 2005 (occasional checks for compiling) (Service Pack 1 recommended)</li>
+</ul>
+<p>Note that WinMerge uses MFC heavily. So free (Express) editions of Visual Studio cannot
+compile WinMerge, unless you have MFC installed separately.</p>
+
+<h4>Libraries</h4>
+<p>WinMerge executable depends on Expat XML parser, SCEW and PCRE libraries.
+All are in the source tree (in <code>/Externals</code> -folder), and need to be
+compiled before compiling WinMerge executable.</p>
+
+<p class="note"><b>Visual Studio 2003.Net and later:</b> You'll need to convert
+library workspace and project files to new format before compiling.</p>
+
+<p> To convert workspace/project files, just open them into Visual Studio and
+let the Visual Studio to convert. Files are:
+<ul>
+ <li><code>Externals\expat\expat.dsw</code></li>
+ <li><code>Externals\scew\win32\scew.dsp</code></li>
+ <li><code>Externals\pcre\pcre.dsw</code></li>
+</ul>
+
+<h4>Additional requirements (out of source tree)</h4>
+<ul>
+ <li>HTML Help Workshop (either stand-alone or from Platform SDK)<br>
+ Download it from :<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/htmlhelp/html/hwMicrosoftHTMLHelpDownloads.asp">
+ HTMLHelp download</a>.</li>
+ <li>Platform SDK - be sure to use version that works with your version of Visual Studio:
+ <ul>
+ <li><strong>VC6</strong>: Platform SDK February 2003 - <a href="http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdk-full.htm">
+ Download and install</a></li>
+ <li><strong>VS2003.Net and later</strong>: Platform SDK Windows 2003 SP1 -
+ <a href="http://www.microsoft.com/downloads/details.aspx?familyid=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB">
+ Download and install</a></li>
+ </ul>
+ Visual Studio 2003.Net and later come with Platform SDK but you may still want more recent version...</li>
+ <li>Installer needs own tools, documented in <a href="readme-InnoSetup.html">readme-InnoSetup.html</a></li>
+ <li>Manual needs Docbook tools, documented in <a href="readme-manual.html">readme-manual.html</a></li>
+</ul>
+
+<h5>Platform SDK components</h5>
+<p>With Feb 2003 Platform SDK (and VC6) following components are needed:</p>
+<ul>
+ <li>Core SDK - obviously..</li>
+ <li>MDAC SDK - for some ODBC etc headers needed by other PSDK headers..</li>
+ <li>Internet Devlopment SDK - for IE/Shell headers</li>
+</ul>
+<p>Basically same components are needed for Windows 2003 SP1 PSDK, but with a different name:</p>
+<ul>
+ <li>Microsoft Windows Core SDK - obviously..</li>
+ <li>Microsoft Data Access Services (MDAC) SDK - for some ODBC etc headers needed by other PSDK headers..</li>
+ <li>Microsoft Web Workshop (IE) SDK - for IE/Shell headers</li>
+</ul>
+<p class="note">If you installed PSDK separately, don't forget to add the PSDK paths to Visual
+Studio's <em>Include</em> and <em>Library</em> directories. The easiest way is to use the
+"<em>Visual Studio Registration\Register PSDK directories with Visual Studio</em>" item from
+the "<em>Platform SDK</em>" start menu folder.</p>
+
+<h3><a name="Buildall_bat">buildall.bat</a></h3>
+<p>There is a <code>buildall.bat</code> in the root folder of source tree. This batch file invokes
+<code>devenv.exe</code> to build (almost) all projects in WinMerge tree. However, it has
+a couple
+of restrictions:
+<ul>
+ <li>It cannot convert project files from VC6 format to newer formats. This must be done first
+ by opening every project to Visual Studio.</li>
+ <li>It cannot build 64-bit shell extension</li>
+</ul></p>
+
+<p>To use <code>buildall.bat</code>:
+<ul>
+ <li>Open Visual Studio Command Prompt (or run <code>vcvars32.bat</code> from Command Prompt).</li>
+ <li>Go to root folder of WinMerge folder structure.</li>
+ <li>Run the batch file.</li>
+</ul></p>
+
+<h3><a name="ProjectFiles">Project files</a></h3>
+<p>Project file for WinMerge executable (in <code>/Src</code>) and other projects like
+ShellExtension (in <code>/ShellExtension</code>) have their own project files. There is no one
+single project/workspace file to compile all projects.<p>
+
+<p>The Visual Studio project file for MSVC6 comes with the WinMerge sources. Newer versions of
+Visual Studio can open that file too, they just ask if one wants to convert to
+the new version.
+The reason we don't ship project files for all Visual Studio versions is we have no resources
+to keep all versions up to date. People can't test all versions themselves, and easily forget
+to update at least one file. So we easily end up in a situation where there is no properly
+working project file at all...</p>
+
+<p>After opening the project file you need to add the HTML Help Workshop path as additional include-
+and library-path.</p>
+
+<p class="note"><b>NOTE:</b> There might be problems compiling/debugging with Visual Studio 2003 when using
+HTML Help WorkShop from the Platform SDK in Visual Studio directory. Download and
+install HTML Workshop as stand-alone and include headers and libraries from standalone
+directory. The probable cause is that including files from Platform SDK directories breaks
+things.</p>
+
+<p class="note"><b>Visual Studio 2003.Net:</b> WinMerge build uses couple of helper batch files
+(<code>Src/PreLink.bat</code> and <code>Src/PostBuild.bat</code>) run from project file.
+Visual Studio adds additional quotation marks to these rules when converting for new version,
+which makes builds to fail. The error is something like <code>The system cannot
+find the batch label specified - ".\..\BuildTmp\MergeUnicodeDebug"</code> where
+the path varies depending on compile target.
+
+<blockquote>Check that rules to call those batch files are like:
+<code>PreLink.bat $(IntDir) $(TargetPath)</code>
+
+<p>without additional quotation marks, like:
+<code>PreLink.bat "$(IntDir)" "$(TargetPath)"</code></blockquote>
+</p>
+
+<h3><a name="Compiling_expat">Compiling expat</a></h3>
+<p>expat is in <code>/Externals/expat</code> folder in source tree. To compile expat:</p>
+<ul>
+ <li>Open Visual Studio workspace <code>/Externals/expat/expat.dsw</code>. If you are
+ using Visual Studio 2003.Net or later you need to convert the file to the new format when
+ Visual Studio opens the file.</li>
+ <li>Select from Visual Studio menu Build / Batch Build</li>
+ <li>Select either debug or release targets.</li>
+ <li>Select Rebuild All</li>
+ </ul>
+
+<p>After build finishes, selected (debug or release) lib and dll files are in
+<code>/Build/expat</code>. WinMerge executable's project file picks them from there.</p>
+
+<h3><a name="Compiling_scew">Compiling scew</a></h3>
+<p>scew is in <code>/Externals/scew</code> folder in source tree. To compile scew:</p>
+<ul>
+ <li>Open Visual Studio project file <code>/Externals/scew/win32/scew.dsp</code> If you are
+ using Visual Studio 2003.Net or later you need to convert the file to the new format when
+ Visual Studio opens the file.</li>
+ <li>Select from Visual Studio menu Build / Batch Build</li>
+ <li>Make sure all targets are selected</li>
+ <li>Select Rebuild All</li>
+</ul>
+
+<h3><a name="Compiling_pcre">Compiling PCRE</a></h3>
+<p>PCRE is in <code>/Externals/pcre</code> folder in source tree. To compile PCRE:</p>
+<ul>
+ <li>Open Visual Studio workspace file <code>/Externals/pcre/pcre.dsw</code> If you are
+ using Visual Studio 2003.Net or later you need to convert the file to the new format when
+ Visual Studio opens the file.</li>
+ <li>Select from Visual Studio menu Build / Batch Build</li>
+ <li>Select <code>config_pcre</code> and <code>pcre</code> projects and build them</li>
+ <li>Select Rebuild All</li>
+ <li><i>Or</i> you can also compile those two projects individually, first
+ <code>config_pcre</code> and then <code>pcre</code> project.
+</ul>
+
+<p>After build finishes, lib and dll files are in <code>/Build/pcre</code>. WinMerge
+executable's project file picks them from there.</p>
+
+<h3><a name="Compiling_core">Compiling WinMerge executable targets</a></h3>
+<p>There are several targets available for compiling different projects. Targets used
+for compiling releases are:<br>
+<ul>
+ <li><code>WinMerge.exe</code> : Release</li>
+ <li><code>WinMergeU.exe</code> : UnicodeRelease</li>
+ <li><code>ShellExtension.dll</code> : Release MinDependency</li>
+ <li><code>ShellExtensionU.dll</code> : Unicode Release MinDependency</li>
+ <li>Plugin dlls : Unicode Release MinDependency</li>
+</ul>
+
+<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
+embeds a manifest file for the executable. And as the WinMerge resource file includes
+a manifest
+file there are conflicts.</p>
+
+<p>The easiest way to fix the compile is to disable VS2005 from creating and embedding
+the manifest file. From project properties:
+<ul>
+ <li>disable Linker / Manifest File / Generate Manifest (set to "No")</li>
+ <li>disable Manifest Tool / Input and Output/ Embed Manifest (set to "No")
+</ul></p>
+
+</body>
+</html>
\ No newline at end of file
Modified: branches/R2_8/Docs/Developers/index.html
===================================================================
--- branches/R2_8/Docs/Developers/index.html 2008-03-28 14:52:01 UTC (rev 5207)
+++ branches/R2_8/Docs/Developers/index.html 2008-03-28 14:56:03 UTC (rev 5208)
@@ -59,6 +59,8 @@
<p><b>Important files:</b>
<ul>
+ <li><a href="Compiling.html">WinMerge compiling</a> contains instructions
+ for setting up development environment and compiling WinMerge.</li>
<li><a href="readme-developers.html">ReadMe for developers</a> is old "main"
document. Contains still lots and lots of useful information.</li>
<li><a href="readme-Subversion.html">Subversion info</a> tells how to use
Modified: branches/R2_8/Docs/Developers/readme-developers.html
===================================================================
--- branches/R2_8/Docs/Developers/readme-developers.html 2008-03-28 14:52:01 UTC (rev 5207)
+++ branches/R2_8/Docs/Developers/readme-developers.html 2008-03-28 14:56:03 UTC (rev 5208)
@@ -51,7 +51,6 @@
<h3>Table of Contents</h3>
<ol>
- <li><a href="#Compiling">Compiling</a></li>
<li><a href="#Code_changes">Code changes</a></li>
<li><a href="#MakePatchDirs">MakePatchDirs</a></li>
<li><a href="#Minor_code_changes_and_bug_fixes">Minor code changes and bug fixes</a></li>
@@ -66,193 +65,7 @@
<li><a href="#ShellExt">Shell Extension</a></li>
</ol>
-<h3><a name="Compiling">Compiling</a></h3>
-<p>Compiling sources is usually the first thing you want to do. Source packages for
-different versions are available from SourceForge.net.</p>
-
-<h3>Environment</h3>
-<h4>Supported Compilers</h4>
-<ul>
- <li>Visual Studio 2003.Net + Service Pack 1 (used for releases)</li>
- <li>Visual Studio 6 + Service Pack 6</li>
- <li>Visual Studio 2005 (occasional checks for compiling) (Service Pack 1 recommended)</li>
-</ul>
-<p>Note that WinMerge uses MFC heavily. So free (Express) editions of Visual Studio cannot
-compile WinMerge, unless you have MFC installed separately.</p>
-
-<h4>Libraries</h4>
-<p>WinMerge executable depends on Expat XML parser, SCEW and PCRE libraries.
-All are in the source tree (in <code>/Externals</code> -folder), and need to be
-compiled before compiling WinMerge executable.</p>
-
-<p class="note"><b>Visual Studio 2003.Net and later:</b> You'll need to convert
-library workspace and project files to new format before compiling.</p>
-
-<p> To convert workspace/project files, just open them into Visual Studio and
-let the Visual Studio to convert. Files are:
-<ul>
- <li><code>Externals\expat\expat.dsw</code></li>
- <li><code>Externals\scew\win32\scew.dsp</code></li>
- <li><code>Externals\pcre\pcre.dsw</code></li>
-</ul>
-
-<h4>Additional requirements (out of source tree)</h4>
-<ul>
- <li>HTML Help Workshop (either stand-alone or from Platform SDK)<br>
- Download it from :<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/htmlhelp/html/hwMicrosoftHTMLHelpDownloads.asp">
- HTMLHelp download</a>.</li>
- <li>Platform SDK - be sure to use version that works with your version of Visual Studio:
- <ul>
- <li><strong>VC6</strong>: Platform SDK February 2003 - <a href="http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdk-full.htm">
- Download and install</a></li>
- <li><strong>VS2003.Net and later</strong>: Platform SDK Windows 2003 SP1 -
- <a href="http://www.microsoft.com/downloads/details.aspx?familyid=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB">
- Download and install</a></li>
- </ul>
- Visual Studio 2003.Net and later come with Platform SDK but you may still want more recent version...</li>
- <li>Installer needs own tools, documented in <a href="readme-InnoSetup.html">readme-InnoSetup.html</a></li>
- <li>Manual needs Docbook tools, documented in <a href="readme-manual.html">readme-manual.html</a></li>
-</ul>
-
-<h5>Platform SDK components</h5>
-<p>With Feb 2003 Platform SDK (and VC6) following components are needed:</p>
-<ul>
- <li>Core SDK - obviously..</li>
- <li>MDAC SDK - for some ODBC etc headers needed by other PSDK headers..</li>
- <li>Internet Devlopment SDK - for IE/Shell headers</li>
-</ul>
-<p>Basically same components are needed for Windows 2003 SP1 PSDK, but with a different name:</p>
-<ul>
- <li>Microsoft Windows Core SDK - obviously..</li>
- <li>Microsoft Data Access Services (MDAC) SDK - for some ODBC etc headers needed by other PSDK headers..</li>
- <li>Microsoft Web Workshop (IE) SDK - for IE/Shell headers</li>
-</ul>
-<p class="note">If you installed PSDK separately, don't forget to add the PSDK paths to Visual
-Studio's <em>Include</em> and <em>Library</em> directories. The easiest way is to use the
-"<em>Visual Studio Registration\Register PSDK directories with Visual Studio</em>" item from
-the "<em>Platform SDK</em>" start menu folder.</p>
-
-<h4>buildall.bat</h4>
-<p>There is a <code>buildall.bat</code> in the root folder of source tree. This batch file invokes
-<code>devenv.exe</code> to build (almost) all projects in WinMerge tree. However, it has
-a couple
-of restrictions:
-<ul>
- <li>It cannot convert project files from VC6 format to newer formats. This must be done first
- by opening every project to Visual Studio.</li>
- <li>It cannot build 64-bit shell extension</li>
-</ul></p>
-
-<p>To use <code>buildall.bat</code>:
-<ul>
- <li>Open Visual Studio Command Prompt (or run <code>vcvars32.bat</code> from Command Prompt).</li>
- <li>Go to root folder of WinMerge folder structure.</li>
- <li>Run the batch file.</li>
-</ul></p>
-
-<h4>Project files</h4>
-<p>Project file for WinMerge executable (in <code>/Src</code>) and other projects like
-ShellExtension (in <code>/ShellExtension</code>) have their own project files. There is no one
-single project/workspace file to compile all projects.<p>
-
-<p>The Visual Studio project file for MSVC6 comes with the WinMerge sources. Newer versions of
-Visual Studio can open that file too, they just ask if one wants to convert to
-the new version.
-The reason we don't ship project files for all Visual Studio versions is we have no resources
-to keep all versions up to date. People can't test all versions themselves, and easily forget
-to update at least one file. So we easily end up in a situation where there is no properly
-working project file at all...</p>
-
-<p>After opening the project file you need to add the HTML Help Workshop path as additional include-
-and library-path.</p>
-
-<p class="note"><b>NOTE:</b> There might be problems compiling/debugging with Visual Studio 2003 when using
-HTML Help WorkShop from the Platform SDK in Visual Studio directory. Download and
-install HTML Workshop as stand-alone and include headers and libraries from standalone
-directory. The probable cause is that including files from Platform SDK directories breaks
-things.</p>
-
-<p class="note"><b>Visual Studio 2003.Net:</b> WinMerge build uses couple of helper batch files
-(<code>Src/PreLink.bat</code> and <code>Src/PostBuild.bat</code>) run from project file.
-Visual Studio adds additional quotation marks to these rules when converting for new version,
-which makes builds to fail. The error is something like <code>The system cannot
-find the batch label specified - ".\..\BuildTmp\MergeUnicodeDebug"</code> where
-the path varies depending on compile target.
-
-<blockquote>Check that rules to call those batch files are like:
-<code>PreLink.bat $(IntDir) $(TargetPath)</code>
-
-<p>without additional quotation marks, like:
-<code>PreLink.bat "$(IntDir)" "$(TargetPath)"</code></blockquote>
-</p>
-
-<h4>Compiling expat</h4>
-<p>expat is in <code>/Externals/expat</code> folder in source tree. To compile expat:</p>
-<ul>
- <li>Open Visual Studio workspace <code>/Externals/expat/expat.dsw</code>. If you are
- using Visual Studio 2003.Net or later you need to convert the file to the new format when
- Visual Studio opens the file.</li>
- <li>Select from Visual Studio menu Build / Batch Build</li>
- <li>Select either debug or release targets.</li>
- <li>Select Rebuild All</li>
- </ul>
-
-<p>After build finishes, selected (debug or release) lib and dll files are in
-<code>/Build/expat</code>. WinMerge executable's project file picks them from there.</p>
-
-<h4>Compiling scew</h4>
-<p>scew is in <code>/Externals/scew</code> folder in source tree. To compile scew:</p>
-<ul>
- <li>Open Visual Studio project file <code>/Externals/scew/win32/scew.dsp</code> If you are
- using Visual Studio 2003.Net or later you need to convert the file to the new format when
- Visual Studio opens the file.</li>
- <li>Select from Visual Studio menu Build / Batch Build</li>
- <li>Make sure all targets are selected</li>
- <li>Select Rebuild All</li>
-</ul>
-
-<h4>Compiling PCRE</h4>
-<p>PCRE is in <code>/Externals/pcre</code> folder in source tree. To compile PCRE:</p>
-<ul>
- <li>Open Visual Studio workspace file <code>/Externals/pcre/pcre.dsw</code> If you are
- using Visual Studio 2003.Net or later you need to convert the file to the new format when
- Visual Studio opens the file.</li>
- <li>Select from Visual Studio menu Build / Batch Build</li>
- <li>Select <code>config_pcre</code> and <code>pcre</code> projects and build them</li>
- <li>Select Rebuild All</li>
- <li><i>Or</i> you can also compile those two projects individually, first
- <code>config_pcre</code> and then <code>pcre</code> project.
-</ul>
-
-<p>After build finishes, lib and dll files are in <code>/Build/pcre</code>. WinMerge
-executable's project file picks them from there.</p>
-
-<h4>Compiling WinMerge executable targets</h4>
-<p>There are several targets available for compiling different projects. Targets used
-for compiling releases are:<br>
-<ul>
- <li><code>WinMerge.exe</code> : Release</li>
- <li><code>WinMergeU.exe</code> : UnicodeRelease</li>
- <li><code>ShellExtension.dll</code> : Release MinDependency</li>
- <li><code>ShellExtensionU.dll</code> : Unicode Release MinDependency</li>
- <li>Plugin dlls : Unicode Release MinDependency</li>
-</ul>
-
-<h4>Visual Studio 2005</h4>
-<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
-embeds a manifest file for the executable. And as the WinMerge resource file includes
-a manifest
-file there are conflicts.</p>
-
-<p>The easiest way to fix the compile is to disable VS2005 from creating and embedding
-the manifest file. From project properties:
-<ul>
- <li>disable Linker / Manifest File / Generate Manifest (set to "No")</li>
- <li>disable Manifest Tool / Input and Output/ Embed Manifest (set to "No")
-</ul></p>
-
<h3><a name="Code_changes">Code changes</a></h3>
<p>Please follow these guidelines when submitting changes to WinMerge sources
Modified: branches/R2_8/Docs/Users/ChangeLog.txt
===================================================================
--- branches/R2_8/Docs/Users/ChangeLog.txt 2008-03-28 14:52:01 UTC (rev 5207)
+++ branches/R2_8/Docs/Users/ChangeLog.txt 2008-03-28 14:56:03 UTC (rev 5208)
@@ -7,6 +7,7 @@
Installer: Updated the side art of the installer application (#1915012)
Update URLs and switch to 2.8 manual (#1919965)
New splash screen (#1914869)
+ Create separate document for compiling WinMerge (#1927502)
BugFix: Installer could create a registry access error (#1909967)
BugFix: The filter text box in Open-dialog sometimes displayed some garbage
data (#1915424)
Modified: branches/R2_8/Docs/index.html
===================================================================
--- branches/R2_8/Docs/index.html 2008-03-28 14:52:01 UTC (rev 5207)
+++ branches/R2_8/Docs/index.html 2008-03-28 14:56:03 UTC (rev 5208)
@@ -68,9 +68,11 @@
<p>Developer documentation is in <code><a href="Developers/index.html">Developers</a>-subfolder</code>.
</p>
-<p><b>Important files in user documentation:</b>
+<p><b>Important files in developer documentation:</b>
<ul>
- <li><a href="Developers/readme-developers.html">ReadMe for developers</a>
+ <li><a href="Developers/Compiling.html">WinMerge compiling</a> contains instructions
+ for setting up development environment and compiling WinMerge.</li>
+ <li><a href="Developers/readme-developers.html">ReadMe for developers</a>
contains lots of development-related information.</li>
<li><a href="Developers/readme-Subversion.html">Subversion info</a></li>
<li><a href="Developers/Translations.html">Translation instructions</a></li>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|