|
From: <ge...@us...> - 2007-03-15 20:37:11
|
Revision: 4165
http://svn.sourceforge.net/winmerge/?rev=4165&view=rev
Author: gerundt
Date: 2007-03-15 13:37:04 -0700 (Thu, 15 Mar 2007)
Log Message:
-----------
PATCH: [ 1681099 ] Add "Plugins" folder to installer doc
Modified Paths:
--------------
trunk/Docs/Developers/Changes.txt
trunk/Docs/Developers/readme-InnoSetup.html
Modified: trunk/Docs/Developers/Changes.txt
===================================================================
--- trunk/Docs/Developers/Changes.txt 2007-03-15 20:11:39 UTC (rev 4164)
+++ trunk/Docs/Developers/Changes.txt 2007-03-15 20:37:04 UTC (rev 4165)
@@ -1,3 +1,7 @@
+2007-03-15 Tim
+ PATCH: [ 1681099 ] Add "Plugins" folder to installer doc
+ Developers: readme-InnoSetup.html
+
2007-02-21 Kimmo
Add pcre.dll and InnoSetup/Runtimes to installer doc
Developers: readme-InnoSetup.html
Modified: trunk/Docs/Developers/readme-InnoSetup.html
===================================================================
--- trunk/Docs/Developers/readme-InnoSetup.html 2007-03-15 20:11:39 UTC (rev 4164)
+++ trunk/Docs/Developers/readme-InnoSetup.html 2007-03-15 20:37:04 UTC (rev 4165)
@@ -103,7 +103,6 @@
<ul>
<li><code>ShellExtensionU.dll</code></li>
<li><code>WinMergeU.exe</code></li>
- <li><code>WinMergeU.exe.Manifest</code></li>
</ul>
</li>
<li>
@@ -155,6 +154,17 @@
</li>
</ul>
</li>
+ <li>
+ <code>Plugins/</code>
+ <ul>
+ <li>
+ <code>dlls/</code>
+ <ul>
+ <li><em>Copy the entire Plugins/dlls folder to here</em></li>
+ </ul>
+ </li>
+ </ul>
+ </li>
</ul>
<p><strong>NOTE</strong><br>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ki...@us...> - 2007-04-05 15:00:53
|
Revision: 4235
http://svn.sourceforge.net/winmerge/?rev=4235&view=rev
Author: kimmov
Date: 2007-04-05 08:00:51 -0700 (Thu, 05 Apr 2007)
Log Message:
-----------
Document buildall.bat in readme-developers
Modified Paths:
--------------
trunk/Docs/Developers/Changes.txt
trunk/Docs/Developers/readme-developers.html
Modified: trunk/Docs/Developers/Changes.txt
===================================================================
--- trunk/Docs/Developers/Changes.txt 2007-04-04 19:02:39 UTC (rev 4234)
+++ trunk/Docs/Developers/Changes.txt 2007-04-05 15:00:51 UTC (rev 4235)
@@ -1,3 +1,7 @@
+2007-04-05 Kimmo
+ Document buildall.bat in readme-developers
+ Developers: readme-developers.html
+
2007-03-15 Tim
PATCH: [ 1681099 ] Add "Plugins" folder to installer doc
Developers: readme-InnoSetup.html
Modified: trunk/Docs/Developers/readme-developers.html
===================================================================
--- trunk/Docs/Developers/readme-developers.html 2007-04-04 19:02:39 UTC (rev 4234)
+++ trunk/Docs/Developers/readme-developers.html 2007-04-05 15:00:51 UTC (rev 4235)
@@ -118,6 +118,23 @@
"<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 root folder of source tree. This batch file invokes
+<code>devenv.exe</code> to build (almost) all projects in WinMerge tree. However, it has 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
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ki...@us...> - 2007-04-06 10:08:01
|
Revision: 4236
http://svn.sourceforge.net/winmerge/?rev=4236&view=rev
Author: kimmov
Date: 2007-04-06 03:07:51 -0700 (Fri, 06 Apr 2007)
Log Message:
-----------
Update Organization.txt to match reality
Modified Paths:
--------------
trunk/Docs/Developers/Changes.txt
trunk/Docs/Developers/Organisation.txt
Modified: trunk/Docs/Developers/Changes.txt
===================================================================
--- trunk/Docs/Developers/Changes.txt 2007-04-05 15:00:51 UTC (rev 4235)
+++ trunk/Docs/Developers/Changes.txt 2007-04-06 10:07:51 UTC (rev 4236)
@@ -1,3 +1,7 @@
+2007-04-06 Kimmo
+ Update Organization.txt to match reality
+ Developers: Organisation.txt
+
2007-04-05 Kimmo
Document buildall.bat in readme-developers
Developers: readme-developers.html
Modified: trunk/Docs/Developers/Organisation.txt
===================================================================
--- trunk/Docs/Developers/Organisation.txt 2007-04-05 15:00:51 UTC (rev 4235)
+++ trunk/Docs/Developers/Organisation.txt 2007-04-06 10:07:51 UTC (rev 4236)
@@ -1,8 +1,7 @@
-WinMerge CVS organisation
+WinMerge Folder Structure
=========================
-WinMerge
- ArchiveSupport
- Merge7z
- Merge7zInstaller
@@ -22,7 +21,7 @@
- InnoSetup
- Art
- Languages
- - Runtimes
+ - Runtimes
- Plugins
- dlls
- Src_Delphi
@@ -48,9 +47,6 @@
- Web
-WinMerge/
- - Module root, no files to here please.
-
WinMerge/ArchiveSupport/
- Archive file support system. Currently includes 7-Zip based archive support.
@@ -80,7 +76,7 @@
- Readme.txt translations
WinMerge/Docs/Users/Manual/
- - New 2.2.x userguide. Using Docbook/XML.
+ - Userguide, using Docbook/XML.
WinMerge/Externals/
- External code modules WinMerge uses
@@ -112,7 +108,7 @@
WinMerge/Installer/InnoSetup/Languages/
- Installer translations
-WinMerge/Installer/InnoSetup/Runtimes/
+WinMerge/Installer/Runtimes/
- Libraries for WinMerge added to install package
WinMerge/Plugins/
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ki...@us...> - 2007-04-08 16:43:13
|
Revision: 4240
http://svn.sourceforge.net/winmerge/?rev=4240&view=rev
Author: kimmov
Date: 2007-04-08 09:43:10 -0700 (Sun, 08 Apr 2007)
Log Message:
-----------
Update Options documentation for latest changes
Modified Paths:
--------------
trunk/Docs/Developers/Changes.txt
trunk/Docs/Developers/Options.html
Modified: trunk/Docs/Developers/Changes.txt
===================================================================
--- trunk/Docs/Developers/Changes.txt 2007-04-08 13:05:01 UTC (rev 4239)
+++ trunk/Docs/Developers/Changes.txt 2007-04-08 16:43:10 UTC (rev 4240)
@@ -1,3 +1,7 @@
+2007-04-08 Kimmo
+ Update Options documentation for latest changes
+ Developers: Options.html
+
2007-04-06 Kimmo
Update Organization.txt to match reality
Developers: Organisation.txt
Modified: trunk/Docs/Developers/Options.html
===================================================================
--- trunk/Docs/Developers/Options.html 2007-04-08 13:05:01 UTC (rev 4239)
+++ trunk/Docs/Developers/Options.html 2007-04-08 16:43:10 UTC (rev 4240)
@@ -53,25 +53,28 @@
<h3>Direct access with WinAPI</h3>
<p>This is handy for settings needed in few events or cases. Especially when
-<code>COptionsMgr</code> is not available, e.g. early in startup of WinMerge.</p>
+<code>COptionsMgr</code> is not available, e.g. early in startup of WinMerge.
+However this method misses all advantages of COptionsMgr, like import/export and
+caching. So it should be used only when really necessary.</p>
<h3>COptionsMgr</h3>
<p>Using <code>COptionsMgr</code> is recommended for all new options. Also all options
visible in Options-dialog must use <code>COptionsMgr</code>. Currently there is one
-<code>COptionsMgr</code> (or actually <code>CRegOptionsMgr</code>) instance in <code>CMainFrame</code>.
-But that can change in future.</p>
+<code>COptionsMgr</code> (or actually <code>CRegOptionsMgr</code>) instance in <code>CMergeApp</code>.
+</p>
<p>Using <code>COptionsMgr</code> is pretty simple and straightforward:</p>
<ul>
<li>All options are accessed by constant names, listed in <code>OptionsDef.h</code>.</li>
<li>
- Options are initialized in <code>CMainFrame::OptionsInit()</code>, located in <code>OptionsInit.cpp</code>.
+ Options are initialized in <code>CMergeApp::OptionsInit()</code>, located in <code>OptionsInit.cpp</code>.
When initialised, type is determined and default value given. If option with that name
does not yet exist, new one is created.
</li>
<li>Option value is read using <code>COptionsMgr::GetBool()</code>, <code>GetInt()</code> or <code>GetString()</code>.</li>
<li>Option value is stored using <code>COptionsMgr::SaveOption()</code>. Note that value is saved to registry immediately.</li>
<li>Option value can be reset to default value using <code>COptionsMgr::GetDefault()</code></li>
+ <li>Option value can be removed using <code>COptionsMgr::RemoveOption()</code></li>
</ul>
<h3>Adding a new option</h3>
@@ -82,7 +85,7 @@
And use meaningful names for options.
</li>
<li>
- Add option initialiser to <code>CMainFrame::OptionsInit()</code>, with sensible
+ Add option initialiser to <code>CMergeApp::OptionsInit()</code>, with sensible
default value. Remember default value is what most users see when first
time using WinMerge or new feature using it. So it really must be good
for normal use.
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ge...@us...> - 2007-04-12 21:49:09
|
Revision: 4251
http://svn.sourceforge.net/winmerge/?rev=4251&view=rev
Author: gerundt
Date: 2007-04-12 14:49:04 -0700 (Thu, 12 Apr 2007)
Log Message:
-----------
PATCH: [ 1699528 ] Translations instructions for dev docs
Modified Paths:
--------------
trunk/Docs/Developers/Changes.txt
Added Paths:
-----------
trunk/Docs/Developers/Translations.html
Modified: trunk/Docs/Developers/Changes.txt
===================================================================
--- trunk/Docs/Developers/Changes.txt 2007-04-12 16:23:11 UTC (rev 4250)
+++ trunk/Docs/Developers/Changes.txt 2007-04-12 21:49:04 UTC (rev 4251)
@@ -1,3 +1,7 @@
+2007-04-12 Tim
+ PATCH: [ 1699528 ] Translations instructions for dev docs
+ Developers new file: Translations.html
+
2007-04-08 Kimmo
Update Options documentation for latest changes
Developers: Options.html
Added: trunk/Docs/Developers/Translations.html
===================================================================
--- trunk/Docs/Developers/Translations.html (rev 0)
+++ trunk/Docs/Developers/Translations.html 2007-04-12 21:49:04 UTC (rev 4251)
@@ -0,0 +1,143 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+ "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+ <title>Translations instructions</title>
+ <meta http-equiv="content-type" content="text/html; charset=UTF-8">
+ <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;
+ }
+ pre {
+ margin-left: 25px;
+ margin-right: 25px;
+ padding: 5px;
+ background-color: #EEEEEE;
+ border: 1px solid black;
+ }
+ p.important {
+ padding: 5px;
+ background-color: #FFDDDD;
+ border: 1px solid red;
+ font-weight: bold;
+ }
+ p.note {
+ padding: 5px;
+ background-color: #DDDDFF;
+ border: 1px solid blue;
+ }
+ -->
+ </style>
+</head>
+<body>
+<h2>Translations instructions</h2>
+<ul>
+ <li><a href="#translate">I want to translate into my own language</a></li>
+ <li><a href="#developer">Instructions for those who know Subversion and Visual C++</a></li>
+ <li><a href="#everybody">Instructions for everybody else</a></li>
+ <li><a href="#shellextension">Translating ShellExtension</a></li>
+ <li><a href="#installer">Translating Installer</a></li>
+ <li><a href="#readme">Translating ReadMe.txt</a></li>
+</ul>
+
+<h3><a name="translate">I want to translate into my own language</a></h3>
+<p>If you are interested in translating WinMerge to your own language, we'd be happy to include your language as well.</p>
+
+<p>All the resources are located in a DLL, so it should be fairly straightforward to support most languages.</p>
+
+<p>We have a list with the <a href="http://winmerge.org/Wiki/index.php?title=Translations">status of current translations</a>, so you can check if your language is already available and/or it needs to be updated.</p>
+
+<p class="important">Please remember WinMerge is an Open Source project. Send translation updates to us as <code>.rc</code> file source patches. We WON't accept modified <code>.lang</code> binary files. We need the sources.</p>
+
+<h3><a name="developer">Instructions for those who know Subversion and Visual C++</a></h3>
+<p>Grab a copy of the source from <a href="http://sourceforge.net/svn/?group_id=13216">Subversion</a>.</p>
+<p>You will need to translate all the strings in <code>Merge.rc</code> to your language. Make a <code>MergeYourLanguage.rc</code> and upload it to SF.net as a patch <a href="http://sourceforge.net/tracker/?group_id=13216&atid=313216">here</a>.
+<p>Then one of the developers will commit it to Subversion and it will be released with the next release.</p>
+<p class="note">Please try to avoid changing dialog layout when translating.
+The layout should be shared by all translations as much as possible, to make merging (and future translation changes) easier.
+You can of course make controls wider to fit longer texts, but you should not move buttons and other controls if not really necessary.<br /><br />
+If you want to improve dialog layout (we welcome UI improvements) you should submit it as src/Merge.rc patch so it will be merged to all translations.</p>
+
+<h3><a name="everybody">Instructions for everybody else</a></h3>
+
+<p>You must translate all the strings inside a file called <code>Merge.rc</code> into your language.</p>
+<p>The easiest way to get a copy of <code>Merge.rc</code> is to go to <a href="http://sourceforge.net/project/showfiles.php?group_id=13216">our download site</a> and download the latest .zip with sources. If you can't find it, then please <a href="mailto:win...@li...">ask us</a> and we will send the file to you.</p>
+
+<p>If you have Visual Studio, then we suggest you use that to do the translation. If you do not have Visual Studio, then here are some instructions for you.</p>
+
+<p>You only have to translate the strings between the quotes in <code>Merge.rc</code>. Here is an example. The English version looks like this:</p>
+
+<pre>
+ CONTROL "Insert &Spaces",IDC_PROP_INSERT_SPACES,"Button",
+ BS_AUTORADIOBUTTON,77,72,59,10
+</pre>
+<p>And here is the translation into Danish:</p>
+<pre>
+ CONTROL "Indsæt &mellemrum",IDC_PROP_INSERT_SPACES,"Button",
+ BS_AUTORADIOBUTTON,77,72,59,10
+</pre>
+
+<p>Here are a couple of rules to follow:</p>
+<ul>
+ <li>Do not translate the first 75 lines.</li>
+ <li>Do not translate anything that is all uppercase letters.</li>
+ <li>
+ The <code>&</code> sign is for accelerator buttons, try to make them meaningful in your language.<br />
+ <em>The Chinese translations handle accelerators by including them in parentheses at the end of the string (and using the English accelerators), eg, "状态栏(&S)".<br />
+ This is per the instructions for double-byte languages given in section "Access Key Definition" in Microsoft's Localization guidelines.</em>
+ </li>
+ <li>Don't translate the following strings, as they have special meaning in Visual C++: <code>"Button"</code>, <code>"MS Sans Serif"</code> and <code>"MS Shell Dlg"</code>.</li>
+</ul>
+
+<p>Please find this line in <code>Merge.rc</code></p>
+<pre>
+ VALUE "FileDescription", "WinMerge Application\0"
+</pre>
+<p>Just before that line, we recommend you put a line like this with your own name in it.</p>
+<pre>
+ VALUE "Comments", "Translated by Christian List\0"
+</pre>
+<p>This ensures that you get credit for the translation. We will of course also add your name to the <a href="http://winmerge.org/Wiki/index.php?title=Translations">status table</a>.</p>
+
+<p>Once you have translated all the strings, then you need to upload your translation to our patch section <a href="http://sourceforge.net/tracker/?group_id=13216&atid=313216">here</a> (please leave your contact information in case there are any problems that need to be resolved). In case you have problems uploading the patch, you can also send it to us by e-mail
+<a href="mailto:win...@li...">here</a>.</p>
+
+<p>Then one of the developers will compile and test your translation; if there are problems, we will contact you to get them resolved. When everything is working your translation will be included in the next release of WinMerge.</p>
+
+<p>When the next major release is imminent, we will notify you again to give you a chance to update the translation with any new/changed strings.</p>
+
+<h3><a name="shellextension">Translating ShellExtension</a></h3>
+<p>ShellExtension can be translated by translating <code>.rc</code> resource file similarly to WinMerge executable.
+ShellExtension resource files are in <code><a href="http://svn.sourceforge.net/winmerge/trunk/ShellExtension/Languages/">WinMerge\ShellExtension\Languages\</a></code> folder.
+There are only few strings to translate so it should be fast to do.</p>
+
+<h3><a name="installer">Translating Installer</a></h3>
+<p>Installer translation files are in <code><a href="http://svn.sourceforge.net/winmerge/trunk/Installer/InnoSetup/Languages/">WinMerge\Installer\InnoSetup\Languages\</a></code> folder.
+Look for a file named by your language. If one does not yet exist, you should look for InnoSetup translations in <a href="http://www.jrsoftware.org/files/istrans/">http://www.jrsoftware.org/files/istrans/</a>.</p>
+
+<p>After you open the file, scroll to end of it, there are few custom strings you
+need to translate. Look for a header <code><strong>[CustomMessages]</strong></code>
+and strings after it.</p>
+
+<p>If you want to change other strings in file, please consider submitting those
+changes upstream to InnoSetup translators so all InnoSetup users may benefit
+from your improvements. We'll pick those updates then also.</p>
+
+<h3><a name="readme">Translating ReadMe.txt</a></h3>
+<p>Please consider translating also <code>ReadMe.txt</code> file - it is shown in end of installer
+and is added to Start-menu. Translated versions of <code>ReadMe.txt</code> are
+in <code><a href="http://svn.sourceforge.net/winmerge/trunk/Docs/Users/Languages/">WinMerge\Docs\Users\Languages\</a></code> folder. And master <code>ReadMe.txt</code> is
+in <code><a href="http://svn.sourceforge.net/winmerge/trunk/Docs/Users/ReadMe.txt">WinMerge\Docs\Users\ReadMe.txt</a></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.
|
|
From: <ge...@us...> - 2007-04-22 19:54:58
|
Revision: 4259
http://svn.sourceforge.net/winmerge/?rev=4259&view=rev
Author: gerundt
Date: 2007-04-22 12:54:54 -0700 (Sun, 22 Apr 2007)
Log Message:
-----------
PATCH: [ 1703303 ] Improve translations instructions
Modified Paths:
--------------
trunk/Docs/Developers/Changes.txt
trunk/Docs/Developers/Translations.html
Modified: trunk/Docs/Developers/Changes.txt
===================================================================
--- trunk/Docs/Developers/Changes.txt 2007-04-18 19:30:35 UTC (rev 4258)
+++ trunk/Docs/Developers/Changes.txt 2007-04-22 19:54:54 UTC (rev 4259)
@@ -1,3 +1,7 @@
+2007-04-22 Tim
+ PATCH: [ 1703303 ] Improve translations instructions
+ Developers: Translations.html
+
2007-04-12 Tim
PATCH: [ 1699528 ] Translations instructions for dev docs
Developers new file: Translations.html
Modified: trunk/Docs/Developers/Translations.html
===================================================================
--- trunk/Docs/Developers/Translations.html 2007-04-18 19:30:35 UTC (rev 4258)
+++ trunk/Docs/Developers/Translations.html 2007-04-22 19:54:54 UTC (rev 4259)
@@ -62,21 +62,24 @@
<h3><a name="developer">Instructions for those who know Subversion and Visual C++</a></h3>
<p>Grab a copy of the source from <a href="http://sourceforge.net/svn/?group_id=13216">Subversion</a>.</p>
-<p>You will need to translate all the strings in <code>Merge.rc</code> to your language. Make a <code>MergeYourLanguage.rc</code> and upload it to SF.net as a patch <a href="http://sourceforge.net/tracker/?group_id=13216&atid=313216">here</a>.
+<p>You will need to translate all the strings in <code>Src\Merge.rc</code> to your language. Make a <code>Merge<em>YourLanguage</em>.rc</code> and upload it to SF.net as a patch <a href="http://sourceforge.net/tracker/?group_id=13216&atid=313216">here</a>.
+If we have already a translation from your language, you will find the file under the <code>Src\Languages\<em>YourLanguage</em>\</code> folder.</p>
<p>Then one of the developers will commit it to Subversion and it will be released with the next release.</p>
<p class="note">Please try to avoid changing dialog layout when translating.
The layout should be shared by all translations as much as possible, to make merging (and future translation changes) easier.
You can of course make controls wider to fit longer texts, but you should not move buttons and other controls if not really necessary.<br /><br />
-If you want to improve dialog layout (we welcome UI improvements) you should submit it as src/Merge.rc patch so it will be merged to all translations.</p>
+If you want to improve dialog layout (we welcome UI improvements) you should submit it as <code>Src\Merge.rc</code> patch so it will be merged to all translations.</p>
<h3><a name="everybody">Instructions for everybody else</a></h3>
<p>You must translate all the strings inside a file called <code>Merge.rc</code> into your language.</p>
<p>The easiest way to get a copy of <code>Merge.rc</code> is to go to <a href="http://sourceforge.net/project/showfiles.php?group_id=13216">our download site</a> and download the latest .zip with sources. If you can't find it, then please <a href="mailto:win...@li...">ask us</a> and we will send the file to you.</p>
+<p>The file <code>Merge.rc</code> is located under the <code>Src\</code> folder in the source code. Just copy the file to <code>Merge<em>YourLanguage</em>.rc</code> and translate it.
+If you only want to improve a current translation, you find the file under the <code>Src\Languages\<em>YourLanguage</em>\</code> folder.</p>
<p>If you have Visual Studio, then we suggest you use that to do the translation. If you do not have Visual Studio, then here are some instructions for you.</p>
-<p>You only have to translate the strings between the quotes in <code>Merge.rc</code>. Here is an example. The English version looks like this:</p>
+<p>You only have to translate the strings between the quotes in <code>Merge<em>YourLanguage</em>.rc</code>. Here is an example. The English version looks like this:</p>
<pre>
CONTROL "Insert &Spaces",IDC_PROP_INSERT_SPACES,"Button",
@@ -100,7 +103,7 @@
<li>Don't translate the following strings, as they have special meaning in Visual C++: <code>"Button"</code>, <code>"MS Sans Serif"</code> and <code>"MS Shell Dlg"</code>.</li>
</ul>
-<p>Please find this line in <code>Merge.rc</code></p>
+<p>Please find this line in <code>Merge<em>YourLanguage</em>.rc</code></p>
<pre>
VALUE "FileDescription", "WinMerge Application\0"
</pre>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ge...@us...> - 2007-04-22 20:37:54
|
Revision: 4260
http://svn.sourceforge.net/winmerge/?rev=4260&view=rev
Author: gerundt
Date: 2007-04-22 13:37:50 -0700 (Sun, 22 Apr 2007)
Log Message:
-----------
Fix SVN links in translations instructions.
Modified Paths:
--------------
trunk/Docs/Developers/Changes.txt
trunk/Docs/Developers/Translations.html
Modified: trunk/Docs/Developers/Changes.txt
===================================================================
--- trunk/Docs/Developers/Changes.txt 2007-04-22 19:54:54 UTC (rev 4259)
+++ trunk/Docs/Developers/Changes.txt 2007-04-22 20:37:50 UTC (rev 4260)
@@ -1,6 +1,8 @@
2007-04-22 Tim
PATCH: [ 1703303 ] Improve translations instructions
Developers: Translations.html
+ Fix SVN links in translations instructions.
+ Developers: Translations.html
2007-04-12 Tim
PATCH: [ 1699528 ] Translations instructions for dev docs
Modified: trunk/Docs/Developers/Translations.html
===================================================================
--- trunk/Docs/Developers/Translations.html 2007-04-22 19:54:54 UTC (rev 4259)
+++ trunk/Docs/Developers/Translations.html 2007-04-22 20:37:50 UTC (rev 4260)
@@ -122,11 +122,11 @@
<h3><a name="shellextension">Translating ShellExtension</a></h3>
<p>ShellExtension can be translated by translating <code>.rc</code> resource file similarly to WinMerge executable.
-ShellExtension resource files are in <code><a href="http://svn.sourceforge.net/winmerge/trunk/ShellExtension/Languages/">WinMerge\ShellExtension\Languages\</a></code> folder.
+ShellExtension resource files are in <code><a href="http://winmerge.svn.sourceforge.net/viewvc/winmerge/trunk/ShellExtension/Languages/">WinMerge\ShellExtension\Languages\</a></code> folder.
There are only few strings to translate so it should be fast to do.</p>
<h3><a name="installer">Translating Installer</a></h3>
-<p>Installer translation files are in <code><a href="http://svn.sourceforge.net/winmerge/trunk/Installer/InnoSetup/Languages/">WinMerge\Installer\InnoSetup\Languages\</a></code> folder.
+<p>Installer translation files are in <code><a href="http://winmerge.svn.sourceforge.net/viewvc/winmerge/trunk/Installer/InnoSetup/Languages/">WinMerge\Installer\InnoSetup\Languages\</a></code> folder.
Look for a file named by your language. If one does not yet exist, you should look for InnoSetup translations in <a href="http://www.jrsoftware.org/files/istrans/">http://www.jrsoftware.org/files/istrans/</a>.</p>
<p>After you open the file, scroll to end of it, there are few custom strings you
@@ -140,7 +140,7 @@
<h3><a name="readme">Translating ReadMe.txt</a></h3>
<p>Please consider translating also <code>ReadMe.txt</code> file - it is shown in end of installer
and is added to Start-menu. Translated versions of <code>ReadMe.txt</code> are
-in <code><a href="http://svn.sourceforge.net/winmerge/trunk/Docs/Users/Languages/">WinMerge\Docs\Users\Languages\</a></code> folder. And master <code>ReadMe.txt</code> is
-in <code><a href="http://svn.sourceforge.net/winmerge/trunk/Docs/Users/ReadMe.txt">WinMerge\Docs\Users\ReadMe.txt</a></code>.</p>
+in <code><a href="http://winmerge.svn.sourceforge.net/viewvc/winmerge/trunk/Docs/Users/Languages/">WinMerge\Docs\Users\Languages\</a></code> folder. And master <code>ReadMe.txt</code> is
+in <code><a href="http://winmerge.svn.sourceforge.net/viewvc/winmerge/trunk/Docs/Users/ReadMe.txt">WinMerge\Docs\Users\ReadMe.txt</a></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.
|
|
From: <ki...@us...> - 2007-06-02 08:03:54
|
Revision: 4314
http://svn.sourceforge.net/winmerge/?rev=4314&view=rev
Author: kimmov
Date: 2007-06-02 01:03:50 -0700 (Sat, 02 Jun 2007)
Log Message:
-----------
In build instructions, use pcre.dsw instead of pcre.dsp
Modified Paths:
--------------
trunk/Docs/Developers/Changes.txt
trunk/Docs/Developers/readme-developers.html
Modified: trunk/Docs/Developers/Changes.txt
===================================================================
--- trunk/Docs/Developers/Changes.txt 2007-06-01 23:40:08 UTC (rev 4313)
+++ trunk/Docs/Developers/Changes.txt 2007-06-02 08:03:50 UTC (rev 4314)
@@ -1,3 +1,7 @@
+2007-06-02 Kimmo
+ In build instructions, use pcre.dsw instead of pcre.dsp
+ Developers: readme-developers.html
+
2007-04-22 Tim
PATCH: [ 1703303 ] Improve translations instructions
Developers: Translations.html
Modified: trunk/Docs/Developers/readme-developers.html
===================================================================
--- trunk/Docs/Developers/readme-developers.html 2007-06-01 23:40:08 UTC (rev 4313)
+++ trunk/Docs/Developers/readme-developers.html 2007-06-02 08:03:50 UTC (rev 4314)
@@ -184,7 +184,7 @@
<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.dsp</code> If you are
+ <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 new format when
Visual Studio opens the file.</li>
<li>Select from Visual Studio menu Build / Batch Build</li>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ki...@us...> - 2007-06-03 11:58:08
|
Revision: 4315
http://svn.sourceforge.net/winmerge/?rev=4315&view=rev
Author: kimmov
Date: 2007-06-03 04:58:00 -0700 (Sun, 03 Jun 2007)
Log Message:
-----------
SourceForge has Feature Requests -list. Update revision ID info.
Modified Paths:
--------------
trunk/Docs/Developers/Changes.txt
trunk/Docs/Developers/readme-developers.html
Modified: trunk/Docs/Developers/Changes.txt
===================================================================
--- trunk/Docs/Developers/Changes.txt 2007-06-02 08:03:50 UTC (rev 4314)
+++ trunk/Docs/Developers/Changes.txt 2007-06-03 11:58:00 UTC (rev 4315)
@@ -1,3 +1,7 @@
+2007-06-03 Kimmo
+ SourceForge has Feature Requests -list. Update revision ID info.
+ Developers: readme-developers.html
+
2007-06-02 Kimmo
In build instructions, use pcre.dsw instead of pcre.dsp
Developers: readme-developers.html
Modified: trunk/Docs/Developers/readme-developers.html
===================================================================
--- trunk/Docs/Developers/readme-developers.html 2007-06-02 08:03:50 UTC (rev 4314)
+++ trunk/Docs/Developers/readme-developers.html 2007-06-03 11:58:00 UTC (rev 4315)
@@ -53,7 +53,7 @@
<li><a href="#Minor_code_changes_and_bug_fixes">Minor code changes and bug fixes</a></li>
<li><a href="#Coding_conventions">Coding conventions</a></li>
<li><a href="#Doxygen_comments">Doxygen comments</a></li>
- <li><a href="#RCS_Ids">RCS Ids</a></li>
+ <li><a href="#Revision_Ids">Revision Ids</a></li>
<li><a href="#File_release_numbers">File release numbers</a></li>
<li><a href="#Packaging_file_releases">Packaging file releases</a></li>
<li><a href="#Tagging_SVN_when_releasing_files">Tagging Subversion when releasing files</a></li>
@@ -228,7 +228,8 @@
<p class="note">Do not waste yours and ours time by submitting large feature patches
before you have made sure the feature is wanted to WinMerge. Communicate with developers,
-either in bug/feature request(rfe) items or preferably in Developers-forum.</p>
+either in bug/feature request(rfe) items or preferably in Developers-forum or Developers-
+mailing list.</p>
<ol>
<li><p>Post development intentions:</p>
@@ -238,11 +239,11 @@
fixing it. If there is no SourceForge bug report, create one.
</li>
<li>
- If you are implementing a new feature, put a note in the SourceForge RFE
- (request for enhancement) that you're implementing it. If there is no
- SourceForge RFE, create one. Alternatively you can discuss about new
- features in Developers-forum. Please use this! It is a lot less work
- wasted when we agree about design first.
+ If you are implementing a new feature, put a note in the SourceForge Feature
+ Request item that you're implementing it. If there is no SourceForge Feature
+ Request item, create one. Alternatively you can discuss about new features
+ in Developers-forum or Developers-mailing list. Please use this! It is a lot
+ less work wasted when we agree about design first.
</li>
</ul>
</li>
@@ -376,22 +377,18 @@
<li>There is ready to use doxygen config file in <code>docs/developers/doxygen.cfg</code></li>
</ul>
-<h3><a name="RCS_Ids">RCS Ids</a></h3>
+<h3><a name="Revision_Ids">Revision IDs</a></h3>
-<p>We have adopted the convention of using RCS id lines near the top of our source
+<p>We have adopted the convention of using Revision ID lines near the top of our source
files (following the doxygen file header comments). Merely add these two lines
-to any new file you add to the repository, and cvs will modify the Id line by
-appending file version and date information at every checkin:</p>
+to any new file you add to the repository, and SVN will modify the Id line by
+appending revision and date information at checkout:</p>
<pre>
-// RCS ID line follows -- this is updated by CVS
+// Revision ID line follows -- this is updated by SVN
// $Id$
</pre>
-<p>Although we are now using Subversion, those lines are still useful. TortoiseSVN
-understands them and adds correct version number and author, as if it was checked out
-from CVS.</p>
-
<h3><a name="File_release_numbers">File release numbers</a></h3>
<p>We are trying to keep a consistent numbering scheme on our file releases,
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ki...@us...> - 2007-11-26 19:56:26
|
Revision: 4795
http://winmerge.svn.sourceforge.net/winmerge/?rev=4795&view=rev
Author: kimmov
Date: 2007-11-26 11:56:19 -0800 (Mon, 26 Nov 2007)
Log Message:
-----------
Rename Organisation.txt to more descriptive SVN_Organisation.txt.
Added Paths:
-----------
trunk/Docs/Developers/SVN_Organisation.txt
Removed Paths:
-------------
trunk/Docs/Developers/Organisation.txt
Deleted: trunk/Docs/Developers/Organisation.txt
===================================================================
--- trunk/Docs/Developers/Organisation.txt 2007-11-26 18:52:30 UTC (rev 4794)
+++ trunk/Docs/Developers/Organisation.txt 2007-11-26 19:56:19 UTC (rev 4795)
@@ -1,183 +0,0 @@
-
-WinMerge Folder Structure
-=========================
-
- - ArchiveSupport
- - Merge7z
- - Merge7zInstaller
- - Docs
- - Developers
- - Logos
- - Users
- - Languages
- - Manual
- - Externals
- - cppunit
- - expat
- - pcre
- - scew
- - Filters
- - Installer
- - InnoSetup
- - Art
- - Languages
- - Runtimes
- - Plugins
- - dlls
- - Src_Delphi
- - Src_VB
- - Src_VCPP
- - ShellExtension
- - Languages
- - Src
- - Common
- - diffutils
- - editlib
- - ExpatMapLib
- - Languages
- - res
- - Testing
- - CppUnit
- - EditorTest
- - selftests
- - Tools
- - diff2winmerge
- - MakePatchDirs
- - MakeResDll
- - Web
-
-
-WinMerge/ArchiveSupport/
- - Archive file support system. Currently includes 7-Zip based archive support.
-
-WinMerge/ArchiveSupport/Merge7z/
- - 7-Zip based archive file support. Integrates to WinMerge executable.
-
-WinMerge/ArchiveSupport/Merge7zInstaller/
- - Installer for archive file support using 7-Zip. Creates an executable
- which installs needed files.
-
-WinMerge/Docs/
- - Directory containing documentation
-
-WinMerge/Docs/Developers/
- - Documentation mostly for developer interest.
- - readme-developers.htm should be read by all working with source code,
- it contains a lot of useful information about practices of
- WinMerge developers.
-
-WinMerge/Docs/Logos/
- - WinMerge logos from Alexander Skinner.
-
-WinMerge/Docs/Users/
- - Documentation files mostly for users interests
-
-WinMerge/Docs/Users/Languages/
- - Readme.txt translations
-
-WinMerge/Docs/Users/Manual/
- - Userguide, using Docbook/XML.
-
-WinMerge/Externals/
- - External code modules WinMerge uses
-
-WinMerge/Externals/cppunit/
- - CppUnit unit-testing suite for C++ <http://cppunit.sourceforge.net/>
-
-WinMerge/Externals/expat/
- - Expat XML parser <http://expat.sourceforge.net/>
-
-WinMerge/Externals/pcre/
- - PCRE - Perl Compatible Regular Expression <http://www.pcre.org/>
-
-WinMerge/Externals/scew/
- - SCEW - Simple C Expat Wrapper <http://www.nongnu.org/scew/>
-
-WinMerge/Filters/
- - File filters are here
-
-WinMerge/Installer/
- - WinMerge installers. Currently we have only Innosetup-based installer.
-
-WinMerge/Installer/InnoSetup/
- - Source files used to create windows installer (with InnoSetup program)
-
-WinMerge/Installer/InnoSetup/Art/
- - Graphics files installer needs
-
-WinMerge/Installer/InnoSetup/Languages/
- - Installer translations
-
-WinMerge/Installer/Runtimes/
- - Libraries for WinMerge added to install package
-
-WinMerge/Plugins/
- - Plugins files. Also plugins documentation at the moment.
-
-WinMerge/Plugins/dlls/
- - Compiled plugins files
-
-WinMerge/Plugins/Src_Delphi/
- - Sources for plugins made with Delphi
-
-WinMerge/Plugins/Src_VB/
- - Sources for plugins made with Visual Basic
-
-WinMerge/Plugins/Src_VCPP/
- - Sources for plugins made with Visual C++
-
-WinMerge/ShellExtension/
- - Files for ShellExtension for WinMerge. Needs also /Src/Common.
-
-WinMerge/ShellExtension/Languages/
- - ShellExtension translations
-
-WinMerge/Src/
- - WinMerge executable sources.
-
-WinMerge/Src/Common/
- - Some common components shared by tools etc.
-
-WinMerge/Src/diffutils/
- - GNU/diffutils sources
-
-WinMerge/Src/editlib/
- - CrystalEditor editor component sources.
-
-WinMerge/Src/ExpatMapLib/
- - Plugin to Expat XML parser for handling character encodings
-
-WinMerge/Src/Languages/
- - WinMerge translations sources.
-
-WinMerge/Src/res/
- - Bitmaps, icons etc.
-
-WinMerge/Testing/
- - WinMerge testing programs and files
-
-WinMerge/Testing/EditorTest/
- - Some tests for CrystalEditor
-
-WinMerge/Testing/selftests/
- - Tests using Perl run WinMerge executable to test compare functionality.
-
-WinMerge/Tools/
- - Tools needed/used with WinMerge development (e.g. language file compiler).
-
-WinMerge/Tools/diff2winmerge/
- - Commandline wrapper for WinMerge executable, offers
- diffutils -style commandline switches (needed by Perl selftests).
-
-WinMerge/Tools/MakePatchDirs/
- - Source files for MakePatchDirs, a program to generate original &
- altered directories
- - Used to create patches to WinMerge source tree, for upload to
- sourceforge patch board
-
-WinMerge/Tools/MakeResDll/
- - Source files for MakeResDll, a command line program used to
- compile the WinMerge language dlls
-
-WinMerge/Web/
- - Homepages.
Copied: trunk/Docs/Developers/SVN_Organisation.txt (from rev 4792, trunk/Docs/Developers/Organisation.txt)
===================================================================
--- trunk/Docs/Developers/SVN_Organisation.txt (rev 0)
+++ trunk/Docs/Developers/SVN_Organisation.txt 2007-11-26 19:56:19 UTC (rev 4795)
@@ -0,0 +1,183 @@
+
+WinMerge Folder Structure
+=========================
+
+ - ArchiveSupport
+ - Merge7z
+ - Merge7zInstaller
+ - Docs
+ - Developers
+ - Logos
+ - Users
+ - Languages
+ - Manual
+ - Externals
+ - cppunit
+ - expat
+ - pcre
+ - scew
+ - Filters
+ - Installer
+ - InnoSetup
+ - Art
+ - Languages
+ - Runtimes
+ - Plugins
+ - dlls
+ - Src_Delphi
+ - Src_VB
+ - Src_VCPP
+ - ShellExtension
+ - Languages
+ - Src
+ - Common
+ - diffutils
+ - editlib
+ - ExpatMapLib
+ - Languages
+ - res
+ - Testing
+ - CppUnit
+ - EditorTest
+ - selftests
+ - Tools
+ - diff2winmerge
+ - MakePatchDirs
+ - MakeResDll
+ - Web
+
+
+WinMerge/ArchiveSupport/
+ - Archive file support system. Currently includes 7-Zip based archive support.
+
+WinMerge/ArchiveSupport/Merge7z/
+ - 7-Zip based archive file support. Integrates to WinMerge executable.
+
+WinMerge/ArchiveSupport/Merge7zInstaller/
+ - Installer for archive file support using 7-Zip. Creates an executable
+ which installs needed files.
+
+WinMerge/Docs/
+ - Directory containing documentation
+
+WinMerge/Docs/Developers/
+ - Documentation mostly for developer interest.
+ - readme-developers.htm should be read by all working with source code,
+ it contains a lot of useful information about practices of
+ WinMerge developers.
+
+WinMerge/Docs/Logos/
+ - WinMerge logos from Alexander Skinner.
+
+WinMerge/Docs/Users/
+ - Documentation files mostly for users interests
+
+WinMerge/Docs/Users/Languages/
+ - Readme.txt translations
+
+WinMerge/Docs/Users/Manual/
+ - Userguide, using Docbook/XML.
+
+WinMerge/Externals/
+ - External code modules WinMerge uses
+
+WinMerge/Externals/cppunit/
+ - CppUnit unit-testing suite for C++ <http://cppunit.sourceforge.net/>
+
+WinMerge/Externals/expat/
+ - Expat XML parser <http://expat.sourceforge.net/>
+
+WinMerge/Externals/pcre/
+ - PCRE - Perl Compatible Regular Expression <http://www.pcre.org/>
+
+WinMerge/Externals/scew/
+ - SCEW - Simple C Expat Wrapper <http://www.nongnu.org/scew/>
+
+WinMerge/Filters/
+ - File filters are here
+
+WinMerge/Installer/
+ - WinMerge installers. Currently we have only Innosetup-based installer.
+
+WinMerge/Installer/InnoSetup/
+ - Source files used to create windows installer (with InnoSetup program)
+
+WinMerge/Installer/InnoSetup/Art/
+ - Graphics files installer needs
+
+WinMerge/Installer/InnoSetup/Languages/
+ - Installer translations
+
+WinMerge/Installer/Runtimes/
+ - Libraries for WinMerge added to install package
+
+WinMerge/Plugins/
+ - Plugins files. Also plugins documentation at the moment.
+
+WinMerge/Plugins/dlls/
+ - Compiled plugins files
+
+WinMerge/Plugins/Src_Delphi/
+ - Sources for plugins made with Delphi
+
+WinMerge/Plugins/Src_VB/
+ - Sources for plugins made with Visual Basic
+
+WinMerge/Plugins/Src_VCPP/
+ - Sources for plugins made with Visual C++
+
+WinMerge/ShellExtension/
+ - Files for ShellExtension for WinMerge. Needs also /Src/Common.
+
+WinMerge/ShellExtension/Languages/
+ - ShellExtension translations
+
+WinMerge/Src/
+ - WinMerge executable sources.
+
+WinMerge/Src/Common/
+ - Some common components shared by tools etc.
+
+WinMerge/Src/diffutils/
+ - GNU/diffutils sources
+
+WinMerge/Src/editlib/
+ - CrystalEditor editor component sources.
+
+WinMerge/Src/ExpatMapLib/
+ - Plugin to Expat XML parser for handling character encodings
+
+WinMerge/Src/Languages/
+ - WinMerge translations sources.
+
+WinMerge/Src/res/
+ - Bitmaps, icons etc.
+
+WinMerge/Testing/
+ - WinMerge testing programs and files
+
+WinMerge/Testing/EditorTest/
+ - Some tests for CrystalEditor
+
+WinMerge/Testing/selftests/
+ - Tests using Perl run WinMerge executable to test compare functionality.
+
+WinMerge/Tools/
+ - Tools needed/used with WinMerge development (e.g. language file compiler).
+
+WinMerge/Tools/diff2winmerge/
+ - Commandline wrapper for WinMerge executable, offers
+ diffutils -style commandline switches (needed by Perl selftests).
+
+WinMerge/Tools/MakePatchDirs/
+ - Source files for MakePatchDirs, a program to generate original &
+ altered directories
+ - Used to create patches to WinMerge source tree, for upload to
+ sourceforge patch board
+
+WinMerge/Tools/MakeResDll/
+ - Source files for MakeResDll, a command line program used to
+ compile the WinMerge language dlls
+
+WinMerge/Web/
+ - Homepages.
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ki...@us...> - 2008-03-29 10:18:43
|
Revision: 5214
http://winmerge.svn.sourceforge.net/winmerge/?rev=5214&view=rev
Author: kimmov
Date: 2008-03-29 03:18:42 -0700 (Sat, 29 Mar 2008)
Log Message:
-----------
PATCH: [ 1928278 ] Docs: Move ShellExt building to compile doc
Modified Paths:
--------------
trunk/Docs/Developers/Compiling.html
trunk/Docs/Developers/readme-developers.html
Modified: trunk/Docs/Developers/Compiling.html
===================================================================
--- trunk/Docs/Developers/Compiling.html 2008-03-29 10:15:01 UTC (rev 5213)
+++ trunk/Docs/Developers/Compiling.html 2008-03-29 10:18:42 UTC (rev 5214)
@@ -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: trunk/Docs/Developers/readme-developers.html
===================================================================
--- trunk/Docs/Developers/readme-developers.html 2008-03-29 10:15:01 UTC (rev 5213)
+++ trunk/Docs/Developers/readme-developers.html 2008-03-29 10:18:42 UTC (rev 5214)
@@ -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.
|
