Skip to content

Commit 91f457d

Browse files
authored
Update README.md
1 parent 12d190e commit 91f457d

File tree

1 file changed

+31
-4
lines changed

1 file changed

+31
-4
lines changed

README.md

Lines changed: 31 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,42 @@
1-
# Sensors tests
1+
# Getting started
2+
## Get a local copy of the repository
3+
```
4+
cd <my-devel-ert-dir>
5+
git clone https://github.com/EPFLRocketTeam/2024_C_AV_RPI.git
6+
```
7+
Then to get the latest version of the submodules, run:
8+
```
9+
git submodule update --init
10+
```
11+
## Start contributing
12+
You want to add a new feature or correct a bug to the main branch ?
13+
- Create a new branch (from main) and publish it:
14+
```
15+
git checkout -b <new-feat-branch>
16+
git push -u origin <new-feat-branch>
17+
```
18+
- Open a pull request on github, from `<new-feat-branch>` to `main`. If you want to be more communicative about the advancement of your task, you can in a first time declare the PR as a draft. When you think your changes are worth being implemented, you can "undraft" it.
19+
- Start bringing changes on your new branch.
20+
- After each commit/push, make sure that your PR can be merged without conflicts, i.e. its status is "able to merge". If a conflict is detected, please don't add any more changes, and try to resolve it (we have faith in you).
21+
- You can check wether your modifications compile on the remote Rpi, by observing the result of the automatic tests, shown at the bottom of your PR. You can also verify it by yourself, by connecting to the Rpi:<br>
22+
Once connected,
23+
```
24+
cd Documents/2024_C_AV_RPI
25+
git checkout <new-feat-branch>
26+
git pull
27+
```
28+
Then, build!
29+
## Build the code
30+
To build the code, you will have to connect to the Rpi via SSH.
231
Once in the repository, execute:
332
```
4-
mkdir build
533
cd build
6-
cmake ..
734
make
835
```
936

1037
Then you can either run the tests individually with:
1138
```
12-
sudo ./[NAME_OF_TEST]_test
39+
sudo ./build/tests/[NAME_OF_TEST]_test
1340
```
1441

1542
Or run all the tests with:

0 commit comments

Comments
 (0)