Skip to content

Commit cc11d08

Browse files
authored
README.md: consistent assumption about STL location (#5332)
1 parent 5dcd917 commit cc11d08

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -379,8 +379,8 @@ steps. Let's assume we want to debug a new feature with tests located in `tests\
379379

380380
As always, build the STL from your branch and run the tests:
381381
```
382-
C:\STL\out\x64> ninja
383-
C:\STL\out\x64> python tests\utils\stl-lit\stl-lit.py -v C:\STL\tests\std\tests\GH_XXXX_meow
382+
C:\Dev\STL\out\x64> ninja
383+
C:\Dev\STL\out\x64> python tests\utils\stl-lit\stl-lit.py -v C:\Dev\STL\tests\std\tests\GH_XXXX_meow
384384
```
385385

386386
Let's assume one of the tests fails an assert and we want to debug that configuration. `stl-lit` will conveniently print
@@ -390,23 +390,23 @@ provide debug symbols: `/Zi /Fdbark.pdb`.
390390
You can replace `bark` with any descriptive name you like. Add these before the `"-link"` option in the command line
391391
and recompile. Example:
392392
```
393-
C:\STL\out\x64>cl "C:\STL\tests\std\tests\GH_XXXX_meow\test.cpp" [... more arguments ...]
394-
"-FeC:\STL\out\x64\tests\std\tests\GH_XXXX_meow\Output\02\GH_XXXX_meow.exe" /Zi /Fdbark.pdb "-link"
393+
C:\Dev\STL\out\x64>cl "C:\Dev\STL\tests\std\tests\GH_XXXX_meow\test.cpp" [... more arguments ...]
394+
"-FeC:\Dev\STL\out\x64\tests\std\tests\GH_XXXX_meow\Output\02\GH_XXXX_meow.exe" /Zi /Fdbark.pdb "-link"
395395
[... more arguments ...]
396396
```
397397

398398
You can now start debugging the test via:
399399
```
400-
devenv "C:\STL\out\x64\tests\std\tests\GH_XXXX_meow\Output\02\GH_XXXX_meow.exe"
401-
"C:\STL\tests\std\tests\GH_XXXX_meow\test.cpp"
400+
devenv "C:\Dev\STL\out\x64\tests\std\tests\GH_XXXX_meow\Output\02\GH_XXXX_meow.exe"
401+
"C:\Dev\STL\tests\std\tests\GH_XXXX_meow\test.cpp"
402402
```
403403

404404
However, this might not work right away, as Visual Studio may complain about a missing `msvcp140_oss.dll`. The reason
405405
is that the STL builds those and other DLLs itself and we should under no circumstances overwrite the installed ones.
406406
If you are testing one of the configurations with dynamic linkage (`/MD` or `/MDd`) the easiest solution is to add the
407407
build folder to your path:
408408
```
409-
set PATH=C:\STL\out\x64\out\bin\amd64;%PATH%
409+
set PATH=C:\Dev\STL\out\x64\out\bin\amd64;%PATH%
410410
```
411411

412412
## Running Tests With Address Sanitizer (ASan)

0 commit comments

Comments
 (0)