File tree 2 files changed +4
-5
lines changed
2 files changed +4
-5
lines changed Original file line number Diff line number Diff line change @@ -79,10 +79,10 @@ for an example of a simple fuzz test.
79
79
- Another example:
80
80
[src/setup_payload/tests/BUILD.gn](https://github.com/project-chip/connectedhomeip/blob/b367512f519e5e109346e81a0d84fd85cd9192f7/src/setup_payload/tests/BUILD.gn#L43)
81
81
82
- - Add to `src /BUILD.gn`
82
+ - Add to `${chip_root} /BUILD.gn`
83
83
84
84
- Add the Fuzzing Target in this part of the code :
85
- [src /BUILD.gn](https://github.com/project-chip/connectedhomeip/blob/b367512f519e5e109346e81a0d84fd85cd9192f7/BUILD.gn#L52)
85
+ [\${chip_root} /BUILD.gn](https://github.com/project-chip/connectedhomeip/blob/b367512f519e5e109346e81a0d84fd85cd9192f7/BUILD.gn#L52)
86
86
87
87
- Add Fuzzing Target like that
88
88
Original file line number Diff line number Diff line change 330
330
bootstrap.sh should be used for for the first setup, activate.sh may be used for
331
331
subsequent setups as it is faster.
332
332
333
- Next build the python wheels and create a venv (called ` py ` here, but any name
334
- may be used)
333
+ Next build the python wheels and create a venv
335
334
336
335
```
337
336
./scripts/build_python.sh -i out/python_env
338
- source py /bin/activate
337
+ source out/python_env /bin/activate
339
338
```
340
339
341
340
Compile chip-tool:
You can’t perform that action at this time.
0 commit comments