Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | More updates to documentation. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
b3eb32438b01506a53e1bb9afd9d0c4b |
| User & Date: | mistachkin 2012-01-22 13:04:38 |
Context
|
2012-01-22
| ||
| 13:21 | Slight mods to the source code instructions. check-in: 4020e66162 user: mistachkin tags: trunk | |
| 13:04 | More updates to documentation. check-in: b3eb32438b user: mistachkin tags: trunk | |
|
2012-01-21
| ||
| 07:13 | Update Eagle script library in Externals to pre-beta22. check-in: e1e1a9456a user: mistachkin tags: trunk | |
Changes
Changes to www/build.wiki.
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
...
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
|
[http://www.jrsoftware.org/isdl.php | Inno Setup 5.4.2] or higher installed
in "%ProgramFiles%\Inno Setup 5" or "%ProgramFiles(x86)%\Inno
Setup 5" for an 64-bit machines. Alternatively, the Inno Setup
directory may be included in the PATH environment variable.
</li>
<li>
The string "<root>" represents the root of your source tree
for the System.Data.SQLite project.
</li>
<li>
The string "<year>" represents the version of Visual Studio
being used (e.g. 2008).
</li>
</ol>
................................................................................
<li>Open a normal command prompt window with "cmd.exe".</li>
<li>Change the current directory to "<root>\Setup".</li>
<li>
Enter the following command to build the binaries for Win32 (x86):
<b>build.bat ReleaseNativeOnly Win32</b><br /><i>You may need to enter the
command "<b>setenv /x86</b>" first if you are using a
"Windows SDK Command Prompt" or "Visual Studio Command
Prompt" window.</i>
</li>
<li>
Make sure everything succeeds with no errors; the log file
"%TEMP%\System.Data.SQLite.Build_ReleaseNativeOnly_Win32_<year>_Unknown.log"
may be checked if any errors should occur.
</li>
<li>
Enter the following command to build the binaries for x64: <b>build.bat
ReleaseNativeOnly x64</b><br /><i>You may need to enter the command
"<b>setenv /x64</b>" first if you are using a "Windows SDK
Command Prompt" or "Visual Studio Command Prompt" window.</i>
</li>
<li>
Make sure everything succeeds with no errors; the log file
"%TEMP%\System.Data.SQLite.Build_ReleaseNativeOnly_x64_<year>_Unknown.log"
may be checked if any errors should occur.
</li>
|
|
>
|
|
|
|
|
|
|
>
|
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
...
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
|
[http://www.jrsoftware.org/isdl.php | Inno Setup 5.4.2] or higher installed
in "%ProgramFiles%\Inno Setup 5" or "%ProgramFiles(x86)%\Inno
Setup 5" for an 64-bit machines. Alternatively, the Inno Setup
directory may be included in the PATH environment variable.
</li>
<li>
The string "<root>" represents the root directory of your
local source tree (i.e. the working check-out directory) for the
System.Data.SQLite project.
</li>
<li>
The string "<year>" represents the version of Visual Studio
being used (e.g. 2008).
</li>
</ol>
................................................................................
<li>Open a normal command prompt window with "cmd.exe".</li>
<li>Change the current directory to "<root>\Setup".</li>
<li>
Enter the following command to build the binaries for Win32 (x86):
<b>build.bat ReleaseNativeOnly Win32</b><br /><i>You may need to
enter the command "<b>setenv /x86</b>" first if you are using
a "Windows SDK Command Prompt" or "Visual Studio Command
Prompt" window.</i>
</li>
<li>
Make sure everything succeeds with no errors; the log file
"%TEMP%\System.Data.SQLite.Build_ReleaseNativeOnly_Win32_<year>_Unknown.log"
may be checked if any errors should occur.
</li>
<li>
Enter the following command to build the binaries for x64: <b>build.bat
ReleaseNativeOnly x64</b><br /><i>You may need to enter the
command"<b>setenv /x64</b>" first if you are using a
"Windows SDK Command Prompt" or "Visual Studio Command
Prompt" window.</i>
</li>
<li>
Make sure everything succeeds with no errors; the log file
"%TEMP%\System.Data.SQLite.Build_ReleaseNativeOnly_x64_<year>_Unknown.log"
may be checked if any errors should occur.
</li>
|
Changes to www/index.wiki.
5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
<td>
<ul>
<li>[./features.wiki | Features]</li>
<li>[./news.wiki | News]</li>
<li>[./support.wiki | Support]</li>
<li>[./downloads.wiki | Downloads]</li>
<li>[./contribute.wiki | Contributing]</li>
<li>[./build.wiki | Build Procedures]</li>
<li>[./test.wiki | Test Procedures]</li>
<li>[./release.wiki | Release Procedures]</li>
</ul>
</td>
</tr>
</table>
|
> |
5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 |
<td>
<ul>
<li>[./features.wiki | Features]</li>
<li>[./news.wiki | News]</li>
<li>[./support.wiki | Support]</li>
<li>[./downloads.wiki | Downloads]</li>
<li>[./contribute.wiki | Contributing]</li>
<li>[./source.wiki | Source Code]</li>
<li>[./build.wiki | Build Procedures]</li>
<li>[./test.wiki | Test Procedures]</li>
<li>[./release.wiki | Release Procedures]</li>
</ul>
</td>
</tr>
</table>
|
Changes to www/release.wiki.
65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 ... 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 ... 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 |
<li>Open a normal command prompt window with "cmd.exe".</li>
<li>Change the current directory to "<root>\Doc".</li>
<li>
Enter the following command to build all the documentation in
[http://en.wikipedia.org/wiki/Microsoft_Compiled_HTML_Help | CHM]
format: <b>tclsh.exe buildChm.tcl</b><br /><i>This assumes that
[http://www.activestate.com/activetcl | ActiveTcl] version 8.4 or later, the
[http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=21138 | HTML Help Workshop],
and [http://ndoc3.sourceforge.net/ | NDoc3] have all been installed using
the default settings.</i>
</li>
</ol>
................................................................................
<ol>
<li>Open a normal command prompt window with "cmd.exe".</li>
<li>Change the current directory to "<root>\Setup".</li>
<li>
Enter the following command to update the sizes and hashes on the downloads
page based on all the built release packages: <b>tclsh.exe
updateFileInfo.tcl</b><br /><i>This assumes that
[http://www.activestate.com/activetcl | ActiveTcl] version 8.4 or later has
been installed using the default settings and that the Fossil binary is
available somewhere along the
[http://en.wikipedia.org/wiki/PATH_%28variable%29 | PATH] (i.e. for
calculating the SHA1 hashes).</i>
</li>
................................................................................
<ol>
<li>Open a normal command prompt window with "cmd.exe".</li>
<li>Change the current directory to "<root>".</li>
<li>
Enter the following command to build the "default" NuGet package:
<b>nuget.exe pack SQLite.nuspec</b><br /><i>This assumes that the
NuGet binary is available somewhere along the
[http://en.wikipedia.org/wiki/PATH_%28variable%29 | PATH].<br />Please refer
to [http://docs.nuget.org/ | NuGet Documentation] for further details.</i>
</li>
<li>
Enter the following command to build the "managed-only" NuGet
package: <b>nuget.exe pack SQLite.MSIL.nuspec</b><br /><i>This assumes
that the NuGet binary is available somewhere along the
[http://en.wikipedia.org/wiki/PATH_%28variable%29 | PATH].<br />Please refer
to [http://docs.nuget.org/ | NuGet Documentation] for further details.</i>
</li>
<li>
Enter the following command to build the NuGet package for x86:
<b>nuget.exe pack SQLite.x86.nuspec</b><br /><i>This assumes that the
NuGet binary is available somewhere along the
[http://en.wikipedia.org/wiki/PATH_%28variable%29 | PATH].<br />Please refer
to [http://docs.nuget.org/ | NuGet Documentation] for further details.</i>
</li>
<li>
Enter the following command to build the NuGet package for x64:
<b>nuget.exe pack SQLite.x64.nuspec</b><br /><i>This assumes that the
NuGet binary is available somewhere along the
[http://en.wikipedia.org/wiki/PATH_%28variable%29 | PATH].<br />Please refer
to [http://docs.nuget.org/ | NuGet Documentation] for further details.</i>
</li>
</ol>
<a name="publishRelease"></a>
<h2>Publish Release</h2>
|
| | | | | | | | | | | |
65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 ... 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 ... 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 |
<li>Open a normal command prompt window with "cmd.exe".</li>
<li>Change the current directory to "<root>\Doc".</li>
<li>
Enter the following command to build all the documentation in
[http://en.wikipedia.org/wiki/Microsoft_Compiled_HTML_Help | CHM]
format: <b>tclsh.exe buildChm.tcl</b><br /><i>This assumes that
[http://www.activestate.com/activetcl | ActiveTcl] version 8.4 or later, the
[http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=21138 | HTML Help Workshop],
and [http://ndoc3.sourceforge.net/ | NDoc3] have all been installed using
the default settings.</i>
</li>
</ol>
................................................................................
<ol>
<li>Open a normal command prompt window with "cmd.exe".</li>
<li>Change the current directory to "<root>\Setup".</li>
<li>
Enter the following command to update the sizes and hashes on the downloads
page based on all the built release packages: <b>tclsh.exe
updateFileInfo.tcl</b><br /><i>This assumes that
[http://www.activestate.com/activetcl | ActiveTcl] version 8.4 or later has
been installed using the default settings and that the Fossil binary is
available somewhere along the
[http://en.wikipedia.org/wiki/PATH_%28variable%29 | PATH] (i.e. for
calculating the SHA1 hashes).</i>
</li>
................................................................................
<ol>
<li>Open a normal command prompt window with "cmd.exe".</li>
<li>Change the current directory to "<root>".</li>
<li>
Enter the following command to build the "default" NuGet package:
<b>nuget.exe pack SQLite.nuspec</b><br /><i>This assumes
that the NuGet binary is available somewhere along the
[http://en.wikipedia.org/wiki/PATH_%28variable%29 | PATH].<br />Please refer
to [http://docs.nuget.org/ | NuGet Documentation] for further details.</i>
</li>
<li>
Enter the following command to build the "managed-only" NuGet
package: <b>nuget.exe pack SQLite.MSIL.nuspec</b><br />
<i>This assumes that the NuGet binary is available somewhere along the
[http://en.wikipedia.org/wiki/PATH_%28variable%29 | PATH].<br />Please refer
to [http://docs.nuget.org/ | NuGet Documentation] for further details.</i>
</li>
<li>
Enter the following command to build the NuGet package for x86:
<b>nuget.exe pack SQLite.x86.nuspec</b><br /><i>This assumes that
the NuGet binary is available somewhere along the
[http://en.wikipedia.org/wiki/PATH_%28variable%29 | PATH].<br />Please refer
to [http://docs.nuget.org/ | NuGet Documentation] for further details.</i>
</li>
<li>
Enter the following command to build the NuGet package for x64:
<b>nuget.exe pack SQLite.x64.nuspec</b><br /><i>This assumes
that the NuGet binary is available somewhere along the
[http://en.wikipedia.org/wiki/PATH_%28variable%29 | PATH].<br />Please refer
to [http://docs.nuget.org/ | NuGet Documentation] for further details.</i>
</li>
</ol>
<a name="publishRelease"></a>
<h2>Publish Release</h2>
|
Added www/source.wiki.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 |
<title>Source Code</title> <p> Follow these steps to obtain the latest (i.e. unreleased) source code for the System.Data.SQLite project. To obtain the latest officially released source code instead, please refer to the [./downloads.wiki | downloads page]. Unless otherwise noted, all steps need to be done in the order specified. </p> <a name="assumptions"></a> <h2>Assumptions & Prerequisites</h2> <p> The string "<root>" represents the directory where you would like the local copy of source tree (i.e. the working check-out directory) for the System.Data.SQLite project to reside (this should be a completely empty directory). </p> <a name="fossil"></a> <h2>Obtain & Install Fossil</h2> <p> [http://www.fossil-scm.org | Fossil] is a computer program that must be installed on your machine before you use it. Fortunately, installing Fossil is very easy. Fossil consists of a single executable file that you simply download and run. For convenience, the Fossil executable file should be placed in a directory present in your [http://en.wikipedia.org/wiki/PATH_%28variable%29 | PATH]. To uninstall Fossil, simply delete the executable file. [http://www.fossil-scm.org/index.html/doc/tip/www/quickstart.wiki | Detailed instructions] for installing and getting started with Fossil are available on the [http://www.fossil-scm.org/ | Fossil website]. </p> <a name="clone"></a> <h2>Clone Repository (Windows)</h2> <ol> <li>Open a normal command prompt window with "cmd.exe".</li> <li>Change the current directory to "<root>".</li> <li> Enter the following command to create a complete clone (i.e. local copy) of the entire source code repository for the System.Data.SQLite project, including the entire check-in history: <b>fossil clone http://system.data.sqlite.org/ sds.fossil</b> </li> <li> The repository itself uses an [http://www.fossil-scm.org/index.html/doc/trunk/www/fileformat.wiki | enduring file format] stored in a single [http://www.fossil-scm.org/index.html/doc/trunk/www/tech_overview.wiki | SQLite database file] with a particular schema. </li> <li> In this case, after executing the <b>[http://www.fossil-scm.org/index.html/help/clone | clone]</b> command, the local clone of the repository will be placed into the "<b>sds.fossil</b>" file in the current directory. </li> </ol> <a name="working"></a> <h2>Working Copy (Windows)</h2> <ol> <li>Open a normal command prompt window with "cmd.exe".</li> <li>Change the current directory to "<root>".</li> <li> Enter the following command to create a complete working copy of all the files that are currently part of the System.Data.SQLite project: <b>fossil open sds.fossil</b> </li> <li> The local source tree should now be ready for use as described in the [./build.wiki | build procedures] and/or [./test.wiki | test procedures]. </li> <li> In the future, to update the working copy with the latest changes from the official System.Data.SQLite repository (i.e. instead of having to re-clone the entire thing), enter the following command from the same directory where a working copy is located: <b>fossil update</b> </li> </ol> |
Changes to www/test.wiki.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 .. 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 .. 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 |
<title>Test Procedures</title>
<a name="assumptions"></a>
<h2>Test Assumptions & Prerequisites</h2>
<ol>
<li>
The string "<root>" represents the root of the source tree
(i.e. the working check-out directory) for the System.Data.SQLite project.
</li>
<li>
The string "<year>" represents the version of Visual Studio
used (e.g. "2008" or "2010") to build the binaries being
tested.
</li>
................................................................................
"<a href="/index.html/dir?name=Externals/Eagle">Externals\Eagle</a>"
directory.
</p>
<p>
The binaries to test must be [./build.wiki | built] or
[./downloads.wiki | downloaded]. If the binaries are downloaded, they must be
placed in the appropriate build output directory (e.g.
"<root>\bin\<year>\<configuration>\bin" for the
separate managed and interop assemblies or
"<root>\bin\<year>\<platform>\<configuration>"
for the mixed-mode assembly).
</p>
<p>
................................................................................
<li>Open a normal command prompt window with "cmd.exe".</li>
<li>Change the current directory to "<root>".</li>
<li>
Enter the following command to run all the unit tests against the binaries
built with a separate managed and interop assembly:
<b>Externals\Eagle\bin\EagleShell.exe -file Tests\all.eagle</b>
</li>
<li>
Enter the following command to run all the unit tests against the binaries
built with a mixed-mode assembly:
<b>Externals\Eagle\bin\EagleShell.exe -initialize -runtimeOption native -file Tests\all.eagle</b>
</li>
<li>
To test binaries built with MSBuild 3.5 or Visual Studio 2008 (i.e. because
the default is to test binaries built with MSBuild 4.0 or Visual Studio
2010) add the following command line argument right after
"Externals\Eagle\bin\EagleShell.exe" in either of the above
command lines:
<b>-preInitialize "set test_year 2008"</b>
</li>
<li>
To test binaries built in the "Debug" build configuration (i.e.
because the default is to test binaries built in the "Release"
build configuration) add the following command line argument right after
"Externals\Eagle\bin\EagleShell.exe" in either of the above
command lines:
<b>-preInitialize "set test_configuration Debug"</b>
</li>
<li>
Make sure all tests pass; the log file
"%TEMP%\EagleShell.exe.test.<pid>.log" may be checked if any
errors should occur. EagleTest should produce "success" messages
very similar to the following:<br /><br />
|
| | > | | | | | |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 .. 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 .. 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 |
<title>Test Procedures</title>
<a name="assumptions"></a>
<h2>Test Assumptions & Prerequisites</h2>
<ol>
<li>
The string "<root>" represents the root directory of your
local source tree (i.e. the working check-out directory) for the
System.Data.SQLite project.
</li>
<li>
The string "<year>" represents the version of Visual Studio
used (e.g. "2008" or "2010") to build the binaries being
tested.
</li>
................................................................................
"<a href="/index.html/dir?name=Externals/Eagle">Externals\Eagle</a>"
directory.
</p>
<p>
The binaries to test must be [./build.wiki | built] or
[./downloads.wiki | downloaded]. If the binaries are downloaded, they must be
placed according to the build output directory structure (e.g.
"<root>\bin\<year>\<configuration>\bin" for the
separate managed and interop assemblies or
"<root>\bin\<year>\<platform>\<configuration>"
for the mixed-mode assembly).
</p>
<p>
................................................................................
<li>Open a normal command prompt window with "cmd.exe".</li>
<li>Change the current directory to "<root>".</li>
<li>
Enter the following command to run all the unit tests against the binaries
built with a separate managed and interop assembly:
<b>Externals\Eagle\bin\EagleShell.exe -file Tests\all.eagle</b>
</li>
<li>
Enter the following command to run all the unit tests against the binaries
built with a mixed-mode assembly:
<b>Externals\Eagle\bin\EagleShell.exe -initialize -runtimeOption native -file Tests\all.eagle</b>
</li>
<li>
To test binaries built with MSBuild 3.5 or Visual Studio 2008 (i.e. because
the default is to test binaries built with MSBuild 4.0 or Visual Studio
2010) add the following command line argument right after
"Externals\Eagle\bin\EagleShell.exe" in either of the above
command lines:
<b>-preInitialize "set test_year 2008"</b>
</li>
<li>
To test binaries built in the "Debug" build configuration (i.e.
because the default is to test binaries built in the "Release"
build configuration) add the following command line argument right after
"Externals\Eagle\bin\EagleShell.exe" in either of the above
command lines:
<b>-preInitialize "set test_configuration Debug"</b>
</li>
<li>
Make sure all tests pass; the log file
"%TEMP%\EagleShell.exe.test.<pid>.log" may be checked if any
errors should occur. EagleTest should produce "success" messages
very similar to the following:<br /><br />
|