Skip to content

Commit

Permalink
Update build.md
Browse files Browse the repository at this point in the history
  • Loading branch information
Leonid Boytsov authored and GitHub committed Jun 3, 2019
1 parent 2613472 commit f1b6a66
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions manual/build.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ C++ (version 8), you may need to type:
export CCX=g++-8 CC=gcc-8
```

To create makeles for a release version of the code, type:
To create makefiles for a release version of the code, type:
```
cmake -DCMAKE_BUILD_TYPE=Release .
```
Expand All @@ -53,26 +53,26 @@ If you did not create any make les before, you can shortcut by typing:
cmake .
```

To create makeles for a debug version of the code, type:
To create makefiles for a debug version of the code, type:
```
cmake -DCMAKE_BUILD_TYPE=Debug .
```

When makeles are created, just type:
When makefiles are created, just type:

```make```

**Important note**: a shortcut command:
``cmake .``
(re)-creates makeles for the previously created build. When you type ``cmake .``
for the first time, it creates release makefiles. However, if you create debug
(re)-creates makefiles for the previously created build. When you type ``cmake .``
for the first time, it creates release makefiles. However, if you create debug
makefiles and then type ``cmake .``, this will not lead to creation of release makefiles!
To prevent this, you need to to delete the cmake cache and makefiles, before
running cmake. For example, you can do the following (assuming the
current directory is similarity search):

```
rm -rf `find . -name CMakeFiles CMakeCache.txt`
rm -rf `find . -name CMakeFiles CMakeCache.txt`
```

Also note that, for some reason, cmake might sometimes ignore environmental
Expand Down Expand Up @@ -108,7 +108,7 @@ The utility ``test_integr`` runs complete implementations of many methods
and checks if several effectiveness and efficiency characteristics
meet the expectations.
The expectations are encoded as an array of instances of the class ``MethodTestCase``
(see [the code here](similarity_search/test/test_integr.cc#L65)).
(see [the code here](/similarity_search/test/test_integr.cc#L65)).
For example, we expect that the recall falls in a certain pre-recorded range.

Because almost all our methods are randomized, there is a great deal of variance
Expand Down

0 comments on commit f1b6a66

Please sign in to comment.