← Back to branch summary

~ubuntu-branches/ubuntu/vivid/db/vivid-proposed

« back to all changes in this revision

Viewing changes to docs/installation/build_win_test.html

  • Committer: Package Import Robot
  • Author(s): Ondřej Surý
  • Date: 2011-12-05 15:44:35 UTC
  • mfrom: (1.1.10)
  • Revision ID: package-import@ubuntu.com-20111205154435-1rqncut9s3wxba1h
Tags: 5.1.29-1
* Add lintian-override for (not)embedded sqlite in MultiArch
* Generated db_signature is different on each arch
* Update priority of db5.1-util and add missing description of
  db5.1_sql
* Add git-buildpackage configuration
* Imported Upstream version 5.1.29

Show diffs side-by-side

added added

removed removed

Lines of Context:
docs/installation/build_win_test.html
39
39
        <dl>
40
40
          <dt>
41
41
            <span class="sect2">
42
 
              <a href="build_win_test.html#id3586782">Building the software needed by the tests</a>
 
42
              <a href="build_win_test.html#idp50534648">Building the software needed by the tests</a>
43
43
            </span>
44
44
          </dt>
45
45
          <dt>
46
46
            <span class="sect2">
47
 
              <a href="build_win_test.html#id3586614">Running the test suite under Windows</a>
 
47
              <a href="build_win_test.html#idp50524944">Running the test suite under Windows</a>
48
48
            </span>
49
49
          </dt>
50
50
          <dt>
57
57
      <p>To build the test suite on Windows platforms, you will need to configure
58
58
Tcl support.  You will also need sufficient main memory (at least 64MB),
59
59
and disk (around 250MB of disk will be sufficient).</p>
60
 
      <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="id3586782"></a>Building the software needed by the tests</h3></div></div></div>
 
60
      <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="idp50534648"></a>Building the software needed by the tests</h3></div></div></div>
61
61
The test suite must be run against a Debug version of
62
62
Berkeley DB, so you will need a Debug version of the Tcl
63
63
libraries.  This involves building Tcl from its source.  See the Tcl
64
64
sources for more information.
65
65
Then build the Tcl API - see
66
66
<a class="xref" href="build_win_tcl.html" title="Building the Tcl API">Building the Tcl API</a> for details.
67
 
<div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="id3586804"></a>Visual Studio 2005 or newer</h4></div></div></div><p>To build for testing, perform the following steps:</p><p>
 
67
<div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="idp50535992"></a>Visual Studio 2005 or newer</h4></div></div></div><p>To build for testing, perform the following steps:</p><p>
68
68
</p><div class="orderedlist"><ol type="1"><li>Open the Berkeley DB solution.</li><li>Ensure that the target configuration is Debug</li><li>Right click the <span class="emphasis"><em>db_tcl</em></span> project in the Solution Explorer, and select <span class="emphasis"><em>Build</em></span>.</li><li>Right click the <span class="emphasis"><em>db_test</em></span> project in the Solution Explorer, and select <span class="emphasis"><em>Build</em></span>.</li></ol></div><p>
69
69
 
70
70
</p></div></div>
72
72
        <div class="titlepage">
73
73
          <div>
74
74
            <div>
75
 
              <h3 class="title"><a id="id3586614"></a>Running the test suite under Windows</h3>
 
75
              <h3 class="title"><a id="idp50524944"></a>Running the test suite under Windows</h3>
76
76
            </div>
77
77
          </div>
78
78
        </div>
126
126
          <div class="titlepage">
127
127
            <div>
128
128
              <div>
129
 
                <h4 class="title"><a id="id3587103"></a>Visual Studio 2005 or newer</h4>
 
129
                <h4 class="title"><a id="idp50553904"></a>Visual Studio 2005 or newer</h4>
130
130
              </div>
131
131
            </div>
132
132
          </div>