System.Data.SQLite: Check-in [e670692d90]

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview

Comment:	Merge updates from trunk.
Downloads:	Tarball \| ZIP archive \| SQL archive
Timelines:	family \| ancestors \| descendants \| both \| preRelease
Files:	files \| file ages \| folders
SHA1:	e670692d906e3462b84f21c2b4c4b4a41a6c4004
User & Date:	mistachkin 2015-07-31 01:16:50

Context

2015-08-18
19:24		Merge updates from trunk. check-in: 24294cb274 user: mistachkin tags: preRelease
2015-07-31
01:16		Merge updates from trunk. check-in: e670692d90 user: mistachkin tags: preRelease
2015-07-30
18:30		Update release procedures wiki page. check-in: fc9062d656 user: mistachkin tags: trunk
18:06		Bump versions and zero out file hashes and sizes. check-in: 0aff30f776 user: mistachkin tags: preRelease

Changes

Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to Setup/updateFileInfo.tcl.


set pattern2 {<a\
    href=".*?/package/.*?/\d+\.\d+\.\d+\.\d+">(.*?)</a>.*?\((\d+?\.\d+?)\
    MiB\).*?sha1: ([0-9A-F]{40})}

set pattern3 {href="/downloads/(.*?)"}
set pattern4 {\(sha1: ([0-9A-F]{40})\)}


#
# NOTE: Grab all the data from the file to be updated.
#
set data [readFile $updateFileName]

#
................................................................................
}

#
# NOTE: Attempt to verify that each file name now has the correct SHA1 hash
#       associated with it on the page.
#
foreach {dummy3 fileName} [regexp -all -inline -nocase -- $pattern3 $data] \
        {dummy4 fileHash} [regexp -all -inline -nocase -- $pattern4 $data] {

  #
  # NOTE: Get the fully qualified file name based on the configured
  #       directory.
  #
  set fullFileName [file join $outputDirectory [file tail $fileName]]

  #
................................................................................
  set fullFileHash [getFileHash $fullFileName]

  if {$fileHash ne $fullFileHash} then {
    puts stdout "ERROR: SHA1 hash mismatch for\
        file \"$fullFileName\", have \"$fileHash\" (from data),\
        need \"$fullFileHash\" (calculated)."
  }








}

#
# NOTE: Write the [modified] data to the file to be updated.
#
if {$count > 0} then {
  writeFile $updateFileName $data
} else {
  puts stdout "WARNING: No changes, update of \"$updateFileName\" skipped."
}








>







 







|
>







 







>
>
>
>
>
>
>
>


set pattern2 {<a\
    href=".*?/package/.*?/\d+\.\d+\.\d+\.\d+">(.*?)</a>.*?\((\d+?\.\d+?)\
    MiB\).*?sha1: ([0-9A-F]{40})}

set pattern3 {href="/downloads/(.*?)"}
set pattern4 {\(sha1: ([0-9A-F]{40})\)}
set pattern5 {\((\d+?\.\d+?) MiB\)}

#
# NOTE: Grab all the data from the file to be updated.
#
set data [readFile $updateFileName]

#
................................................................................
}

#
# NOTE: Attempt to verify that each file name now has the correct SHA1 hash
#       associated with it on the page.
#
foreach {dummy3 fileName} [regexp -all -inline -nocase -- $pattern3 $data] \
        {dummy4 fileHash} [regexp -all -inline -nocase -- $pattern4 $data] \
        {dummy5 fileSize} [regexp -all -inline -nocase -- $pattern5 $data] {
  #
  # NOTE: Get the fully qualified file name based on the configured
  #       directory.
  #
  set fullFileName [file join $outputDirectory [file tail $fileName]]

  #
................................................................................
  set fullFileHash [getFileHash $fullFileName]

  if {$fileHash ne $fullFileHash} then {
    puts stdout "ERROR: SHA1 hash mismatch for\
        file \"$fullFileName\", have \"$fileHash\" (from data),\
        need \"$fullFileHash\" (calculated)."
  }

  set fullFileSize [getFileSize $fullFileName]

  if {$fileSize ne $fullFileSize} then {
    puts stdout "ERROR: Byte size mismatch for\
        file \"$fullFileName\", have \"$fileSize\" (from data),\
        need \"$fullFileSize\" (calculated)."
  }
}

#
# NOTE: Write the [modified] data to the file to be updated.
#
if {$count > 0} then {
  writeFile $updateFileName $data
} else {
  puts stdout "WARNING: No changes, update of \"$updateFileName\" skipped."
}

Changes to www/downloads.wiki.

      </td>
    </tr>

    <tr>
      <td width="10">&nbsp;</td>
      <td width="30%" valign="top" align="right">
        <a href="http://www.sourceforge.net/projects/sqlite-dotnet2/files/SQLite%20for%20ADO.NET%202.0/1.0.66.0/SQLite-1.0.66.0-setup.exe/download">SQLite-1.0.66.0-setup.exe</a>
        <br />
        (0.00 MiB)
      </td>
      <td width="5"></td>
      <td valign="top">
        Legacy versions, as well as the original support forums, may still be
        found at
        <a href="http://sqlite.phxsoftware.com/">http://sqlite.phxsoftware.com/</a>,
        though there have been no updates to this version since April of 2010.

<
<

      </td>
    </tr>

    <tr>
      <td width="10">&nbsp;</td>
      <td width="30%" valign="top" align="right">
        <a href="http://www.sourceforge.net/projects/sqlite-dotnet2/files/SQLite%20for%20ADO.NET%202.0/1.0.66.0/SQLite-1.0.66.0-setup.exe/download">SQLite-1.0.66.0-setup.exe</a>


      </td>
      <td width="5"></td>
      <td valign="top">
        Legacy versions, as well as the original support forums, may still be
        found at
        <a href="http://sqlite.phxsoftware.com/">http://sqlite.phxsoftware.com/</a>,
        though there have been no updates to this version since April of 2010.

Changes to www/release.wiki.

    Enter the following commands to build all the x86 and x64 binaries:
    <br />
    <br />
    <b>SET BUILD_DEBUG=1</b>
    <br />
    <b>build_all.bat</b>
  </li>





</ol>

<a name="testBinaries"></a>
<h2>Test x86 &amp; x64 Binaries</h2>

<ol>
  <li>
................................................................................
    <br />
    <br />
    <b>SET TEST_DEBUG=1</b>
    <br />
    <b>test_all.bat</b>
  </li>






  <li>
    Locate a machine with a processor architecture different from the one tested
    in the previous step and then repeat all the previous steps.
  </li>
</ol>

<a name="buildCeBinaries"></a>
................................................................................
    <b>build_ce_2013.bat</b>
    <br />
    <br />
    <i>This assumes that Visual Studio 2012, &quot;<b>Professional</b>&quot;
    edition or &quot;better&quot; and the Windows Embedded Compact 2013 Toolkit
    are installed.</i>
  </li>





</ol>

<a name="testCeBinariesAutomated"></a>
<h2>Test Windows CE Binaries via Automation</h2>

<ol>
  <li>
................................................................................
  <li>
    Enter the following command to test all the binaries available for Windows
    CE:
    <br />
    <br />
    <b>test_ce_200x.bat</b>
  </li>





</ol>

<a name="testCeBinariesManually"></a>
<h2>Test Windows CE Binaries Manually</h2>

<ol>
  <li>
................................................................................
    <br />
    <i>This assumes that [https://www.activestate.com/activetcl | ActiveTcl]
    version 8.4 or later, the
    [https://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>

<a name="buildSetupPackages"></a>
<h2>Build Setup Release Packages</h2>

<ol>
  <li>Open a normal command prompt window with &quot;cmd.exe&quot;.</li>
................................................................................
    Enter the following commands to build all the setup packages for x86 and x64:
    <br />
    <br />
    <b>SET BAKE_DEBUG=1</b>
    <br />
    <b>bake_all.bat</b>
  </li>





</ol>

<a name="buildBinaryPackages"></a>
<h2>Build x86 &amp; x64 Binary Release Packages</h2>

<ol>
  <li>Open a normal command prompt window with &quot;cmd.exe&quot;.</li>
................................................................................
    and x64:
    <br />
    <br />
    <b>SET RELEASE_DEBUG=1</b>
    <br />
    <b>release_all.bat</b>
  </li>





</ol>

<a name="buildStaticBinaryPackages"></a>
<h2>Build x86 &amp; x64 Static Binary Release Packages</h2>

<ol>
  <li>Open a normal command prompt window with &quot;cmd.exe&quot;.</li>
................................................................................
    for x86 and x64:
    <br />
    <br />
    <b>SET RELEASE_DEBUG=1</b>
    <br />
    <b>release_static.bat</b>
  </li>





</ol>

<a name="buildCeBinaryPackages"></a>
<h2>Build Windows CE Binary Release Packages</h2>

<ol>
  <li>Open a normal command prompt window with &quot;cmd.exe&quot;.</li>
................................................................................
    Windows Embedded Compact 2013:
    <br />
    <br />
    <b>SET RELEASE_DEBUG=1</b>
    <br />
    <b>release_ce_2013.bat</b>
  </li>





</ol>

<a name="buildSourcePackages"></a>
<h2>Build Source Release Packages</h2>

<ol>
  <li>Open a normal command prompt window with &quot;cmd.exe&quot;.</li>
................................................................................

  <li>
    Enter the following command to build all the source release packages:
    <br />
    <br />
    <b>archive.bat</b>
  </li>





</ol>

<a name="verifyAllPackages"></a>
<h2>Verify All Release Packages</h2>

<ol>
  <li>Open a normal command prompt window with &quot;cmd.exe&quot;.</li>
................................................................................
    <i>This assumes that the <a href="https://www.fossil-scm.org/">Fossil</a>,
    <a href="https://sourceforge.net/projects/innounp/">Inno Setup Unpacker</a>,
    <a href="http://www.rarlab.com/">UnRAR</a>, and
    <a href="http://www.info-zip.org/">UnZip</a> binaries are available in the
    locations specified via the &quot;FossilTool&quot;,
    &quot;InnoUnpackTool&quot;, &quot;UnRARTool&quot;, and &quot;UnZipTool&quot;
    environment variables, respectively.</i>





    <br />
    <br />
    <i>If errors are generated, the file
    &quot;&lt;root&gt;\Setup\data\verify.lst&quot; may need to be updated to
    account for the files that have been added and/or removed from the release
    archives since the previous release.</i>
  </li>
................................................................................
    <b>build_nuget.bat</b>
    <br />
    <br />
    <i>This assumes that the NuGet binary is available somewhere along the
    [https://en.wikipedia.org/wiki/PATH_%28variable%29 | PATH].<br />Please refer
    to [https://docs.nuget.org/ | NuGet Documentation] for further details.</i>
  </li>





</ol>

<a name="updateDownloadsPage"></a>
<h2>Update Downloads Page</h2>

<ol>
  <li>Open a normal command prompt window with &quot;cmd.exe&quot;.</li>
................................................................................
    <br />
    <i>This assumes that [https://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
    [https://en.wikipedia.org/wiki/PATH_%28variable%29 | PATH] (i.e. for
    calculating the SHA1 hashes).</i>
  </li>





</ol>

<a name="publishRelease"></a>
<h2>Publish Release</h2>

<ol>
  <li>Upload all the release packages to the web site.</li>








>
>
>
>
>







 







>
>
>
>
>







 







>
>
>
>
>







 







>
>
>
>
>







 







>
>
>
>
>







 







>
>
>
>
>







 







>
>
>
>
>







 







>
>
>
>
>







 







>
>
>
>
>







 







>
>
>
>
>







 







>
>
>
>
>







 







>
>
>
>
>







 







>
>
>
>
>

    Enter the following commands to build all the x86 and x64 binaries:
    <br />
    <br />
    <b>SET BUILD_DEBUG=1</b>
    <br />
    <b>build_all.bat</b>
  </li>

  <li>
    Make sure everything succeeds with no errors; the console output may be
    checked if any errors should occur.
  </li>
</ol>

<a name="testBinaries"></a>
<h2>Test x86 &amp; x64 Binaries</h2>

<ol>
  <li>
................................................................................
    <br />
    <br />
    <b>SET TEST_DEBUG=1</b>
    <br />
    <b>test_all.bat</b>
  </li>

  <li>
    Make sure everything succeeds with no errors; the console output may be
    checked if any errors should occur.
  </li>

  <li>
    Locate a machine with a processor architecture different from the one tested
    in the previous step and then repeat all the previous steps.
  </li>
</ol>

<a name="buildCeBinaries"></a>
................................................................................
    <b>build_ce_2013.bat</b>
    <br />
    <br />
    <i>This assumes that Visual Studio 2012, &quot;<b>Professional</b>&quot;
    edition or &quot;better&quot; and the Windows Embedded Compact 2013 Toolkit
    are installed.</i>
  </li>

  <li>
    Make sure everything succeeds with no errors; the console output may be
    checked if any errors should occur.
  </li>
</ol>

<a name="testCeBinariesAutomated"></a>
<h2>Test Windows CE Binaries via Automation</h2>

<ol>
  <li>
................................................................................
  <li>
    Enter the following command to test all the binaries available for Windows
    CE:
    <br />
    <br />
    <b>test_ce_200x.bat</b>
  </li>

  <li>
    Make sure everything succeeds with no errors; the console output may be
    checked if any errors should occur.
  </li>
</ol>

<a name="testCeBinariesManually"></a>
<h2>Test Windows CE Binaries Manually</h2>

<ol>
  <li>
................................................................................
    <br />
    <i>This assumes that [https://www.activestate.com/activetcl | ActiveTcl]
    version 8.4 or later, the
    [https://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>

  <li>
    Make sure everything succeeds with no errors; the console output may be
    checked if any errors should occur.
  </li>
</ol>

<a name="buildSetupPackages"></a>
<h2>Build Setup Release Packages</h2>

<ol>
  <li>Open a normal command prompt window with &quot;cmd.exe&quot;.</li>
................................................................................
    Enter the following commands to build all the setup packages for x86 and x64:
    <br />
    <br />
    <b>SET BAKE_DEBUG=1</b>
    <br />
    <b>bake_all.bat</b>
  </li>

  <li>
    Make sure everything succeeds with no errors; the console output may be
    checked if any errors should occur.
  </li>
</ol>

<a name="buildBinaryPackages"></a>
<h2>Build x86 &amp; x64 Binary Release Packages</h2>

<ol>
  <li>Open a normal command prompt window with &quot;cmd.exe&quot;.</li>
................................................................................
    and x64:
    <br />
    <br />
    <b>SET RELEASE_DEBUG=1</b>
    <br />
    <b>release_all.bat</b>
  </li>

  <li>
    Make sure everything succeeds with no errors; the console output may be
    checked if any errors should occur.
  </li>
</ol>

<a name="buildStaticBinaryPackages"></a>
<h2>Build x86 &amp; x64 Static Binary Release Packages</h2>

<ol>
  <li>Open a normal command prompt window with &quot;cmd.exe&quot;.</li>
................................................................................
    for x86 and x64:
    <br />
    <br />
    <b>SET RELEASE_DEBUG=1</b>
    <br />
    <b>release_static.bat</b>
  </li>

  <li>
    Make sure everything succeeds with no errors; the console output may be
    checked if any errors should occur.
  </li>
</ol>

<a name="buildCeBinaryPackages"></a>
<h2>Build Windows CE Binary Release Packages</h2>

<ol>
  <li>Open a normal command prompt window with &quot;cmd.exe&quot;.</li>
................................................................................
    Windows Embedded Compact 2013:
    <br />
    <br />
    <b>SET RELEASE_DEBUG=1</b>
    <br />
    <b>release_ce_2013.bat</b>
  </li>

  <li>
    Make sure everything succeeds with no errors; the console output may be
    checked if any errors should occur.
  </li>
</ol>

<a name="buildSourcePackages"></a>
<h2>Build Source Release Packages</h2>

<ol>
  <li>Open a normal command prompt window with &quot;cmd.exe&quot;.</li>
................................................................................

  <li>
    Enter the following command to build all the source release packages:
    <br />
    <br />
    <b>archive.bat</b>
  </li>

  <li>
    Make sure everything succeeds with no errors; the console output may be
    checked if any errors should occur.
  </li>
</ol>

<a name="verifyAllPackages"></a>
<h2>Verify All Release Packages</h2>

<ol>
  <li>Open a normal command prompt window with &quot;cmd.exe&quot;.</li>
................................................................................
    <i>This assumes that the <a href="https://www.fossil-scm.org/">Fossil</a>,
    <a href="https://sourceforge.net/projects/innounp/">Inno Setup Unpacker</a>,
    <a href="http://www.rarlab.com/">UnRAR</a>, and
    <a href="http://www.info-zip.org/">UnZip</a> binaries are available in the
    locations specified via the &quot;FossilTool&quot;,
    &quot;InnoUnpackTool&quot;, &quot;UnRARTool&quot;, and &quot;UnZipTool&quot;
    environment variables, respectively.</i>
  </li>

  <li>
    Make sure everything succeeds with no errors; the console output may be
    checked if any errors should occur.
    <br />
    <br />
    <i>If errors are generated, the file
    &quot;&lt;root&gt;\Setup\data\verify.lst&quot; may need to be updated to
    account for the files that have been added and/or removed from the release
    archives since the previous release.</i>
  </li>
................................................................................
    <b>build_nuget.bat</b>
    <br />
    <br />
    <i>This assumes that the NuGet binary is available somewhere along the
    [https://en.wikipedia.org/wiki/PATH_%28variable%29 | PATH].<br />Please refer
    to [https://docs.nuget.org/ | NuGet Documentation] for further details.</i>
  </li>

  <li>
    Make sure everything succeeds with no errors; the console output may be
    checked if any errors should occur.
  </li>
</ol>

<a name="updateDownloadsPage"></a>
<h2>Update Downloads Page</h2>

<ol>
  <li>Open a normal command prompt window with &quot;cmd.exe&quot;.</li>
................................................................................
    <br />
    <i>This assumes that [https://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
    [https://en.wikipedia.org/wiki/PATH_%28variable%29 | PATH] (i.e. for
    calculating the SHA1 hashes).</i>
  </li>

  <li>
    Make sure everything succeeds with no errors; the console output may be
    checked if any errors should occur.
  </li>
</ol>

<a name="publishRelease"></a>
<h2>Publish Release</h2>

<ol>
  <li>Upload all the release packages to the web site.</li>