You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Contributing.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ Ideally, try to add packages to all of these platforms. The name of the package
28
28
Sometimes, it may be required to patch the packages. An example of how to do so can be found in [this PR](https://github.com/RoboStack/ros-noetic/pull/32). Generating the patch can be done as follows:
29
29
30
30
1. Modify the `vinca_*.yaml` file, but just adding the package you want to create the patch for
31
-
2. Run `pixi run build`. This will either succeded it the package can be built without any patch, or fail if a patch is required to actually build the package.
31
+
2. Run `pixi run build`. This will either succeded if the package can be built without any patch, or fail if a patch is required to actually build the package.
32
32
4. Start a shell and go inside the repository to be edited. It should be located in `<robostack folder>/output/src_cache/<repo_name>`, where `<robostack folder>` is the folder where you run `pixi run build` and `<repo_name>` is the name of the repository associated to the package in the `url:` attribute of the repo in the `rosdistro_snapshot.yaml`
33
33
5. Apply the changes that you would like to store into the patch
34
34
6. Create a patch file with `git diff > changes.patch`
@@ -53,15 +53,15 @@ Clone the relevant repo:
53
53
54
54
```bash
55
55
git clone https://github.com/RoboStack/ros-humble.git # or: git clone https://github.com/RoboStack/ros-noetic.git or git clone https://github.com/RoboStack/ros-jazzy.git or git clone https://github.com/RoboStack/ros-kilted.git
56
-
```bash
56
+
```
57
57
58
58
Then move in the newly cloned repo, and if necessary do any change to the `vinca_*.yaml` file for your platform:
59
59
60
60
```bash
61
61
cd ros-humble # or: cd ros-noetic or cd ros-jazzy or cd ros-kilted
62
-
```bash
62
+
```
63
63
64
-
then you can build the packages that need to be built after the `vinca_***.yaml` changes with:
64
+
Then you can build the packages that need to be built after the `vinca_***.yaml` changes with:
0 commit comments