System.Data.SQLite
Check-in [e69b9c401c]
Not logged in

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

Overview
Comment:Updates to the build instructions.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: e69b9c401c8edc3f226b7ee463ee1d50f408e89e
User & Date: shaneh 2011-04-12 15:23:23
Context
2011-04-12
16:03
Fix post-build conditional for XCOPY task. Remove superfluous ItemGroup for embedded resources from LINQ projects. check-in: c584d03d83 user: mistachkin tags: trunk
15:23
Updates to the build instructions. check-in: e69b9c401c user: shaneh tags: trunk
12:42
Increase version number to 3.7.6 and 1.0.69.0 in preparation for the upcoming release. check-in: 1da75aaa06 user: shaneh tags: trunk
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to www/build.wiki.

     7      7   Unless otherwise noted, all steps need to be done in the order specified.
     8      8   </p>
     9      9   
    10     10   <p>You will need a Visual Studio 2008, 2010, or 2010 SP1 development environment for this build.</p>
    11     11   
    12     12   <p>
    13     13   Thanks to the hard work of Joe Mistachkin, the build environment has been setup
    14         -using modular solution and property files.  SQLite.NET.2008.sln is the top level solution
    15         -for VS2008 and SQLite.NET.2010.sln for VS2010.  In general, files with 2008 in the 
    16         -name (eg. SQLite.Interop.2008.vcproj) or files ending in .vsprops are 
    17         -project and property files for the VS2008 solution.  Files with 2010 in the 
    18         -name (eg. SQLite.Interop.2010.vcxproj) or files ending in .props are 
           14  +using modular solution and property files.
           15  +<ul>
           16  +SQLite.NET.2008.sln is the top level solution for VS2008.<br />
           17  +SQLite.NET.2010.sln is the top level solution for VS2010.<br />
           18  +</ul>
           19  +<p>In general, files with 2008 in the name (eg. SQLite.Interop.2008.vcproj) 
           20  +or files ending in .vsprops are project and property files for the VS2008 solution. 
           21  +Files with 2010 in the name (eg. SQLite.Interop.2010.vcxproj) or files ending in .props are 
    19     22   property and project files for the VS2010 solution.  When making changes, 
    20     23   you should make changes to both to keep them in sync.
    21     24   </p>
    22     25   
    23     26   <p>
    24     27   You can either manually build the SDS using the supplied Visual Studio solutions,
    25     28   or follow the steps outlined in the Build Automation section below.
................................................................................
   137    140     <li>Make sure everything succeeds with no errors.  InnoSetup should produce
   138    141     "success" messages very similar to the following:
   139    142   
   140    143     Successful compile (X.XXX sec). Resulting Setup program filename is:
   141    144     </li>
   142    145   </ol>
   143    146   
   144         -<h3><a name="build.bat">build.bat Desription</a></h3>
          147  +<a name="build.bat"></a>
          148  +<h3>build.bat Desription</h3>
   145    149   
   146    150   <p>
   147    151     build.bat is the top level batch file for build automation and should be called
   148    152     with the configuration and platform to build:
   149    153     <ul>
   150         -    build.bat &lt;CONFIGURATION&gt; &lt;PLATFORM&gt;<br>
          154  +    build.bat &lt;CONFIGURATION&gt; &lt;PLATFORM&gt;<br />
   151    155     </ul>
   152    156     This starts by setting 3 environment variables:
   153    157     <ul>
   154         -    ROOT (eg. &lt;pwd&gt;\..)<br>
   155         -    CONFIGURATION (eg. ReleaseNativeOnly)<br>
   156         -    PLATFORM (eg. Win32)<br>
          158  +    ROOT (eg. &lt;pwd&gt;\..)<br />
          159  +    CONFIGURATION (eg. ReleaseNativeOnly)<br />
          160  +    PLATFORM (eg. Win32)<br />
   157    161     </ul>
   158    162     These are used to call another .bat file (eg. set_ReleaseNativeOnly_x64.bat)
   159    163     which calls set_ReleaseNativeOnly.bat to setup more variables to specify
   160    164     which .NET Framework to use:
   161    165     <ul>
   162         -    NETFX35ONLY=1 - set from set_ReleaseNativeOnly.bat<br>
   163         -    YEAR=2008 - set from set_ReleaseNativeOnly.bat<br>
   164         -    YEARS=%YEAR% - set from set_ReleaseNativeOnly.bat<br>
          166  +    NETFX35ONLY=1 - set from set_ReleaseNativeOnly.bat<br />
          167  +    YEAR=2008 - set from set_ReleaseNativeOnly.bat<br />
          168  +    YEARS=%YEAR% - set from set_ReleaseNativeOnly.bat<br />
   165    169     </ul>
   166    170     build.bat attempts to set additional variables based on the chosen
   167    171     and available .NET Framework.
   168    172     <ul>
   169         -    YEAR (eg. 2008)<br>
   170         -    FRAMEWORKDIR (eg. %windir%\Microsoft.NET\Framework\v3.5)<br>
          173  +    YEAR (eg. 2008)<br />
          174  +    FRAMEWORKDIR (eg. %windir%\Microsoft.NET\Framework\v3.5)<br />
   171    175     </ul>
   172         -  The PATH variable is updated to include the directory specified by FRAMEWORKDIR.<br>
          176  +  The PATH variable is updated to include the directory specified by FRAMEWORKDIR.<br />
   173    177     At this point, several variables are setup for the call to 
   174    178     [http://msdn.microsoft.com/en-us/library/0k6kkbsd.aspx | MSBuild]
   175    179     <ul>
   176    180       SOLUTION (eg. .\SQLite.NET.2008.sln)
   177    181       TARGET (eg. Rebuild)
   178    182       LOGGING
   179    183     </ul>
   180    184     MSBuild.exe is called to build the solution.
   181    185   </p>
   182    186