Skip to content

Commit c186e7c

Browse files
authored
Update commands for local testing
1 parent 1bfc1a6 commit c186e7c

File tree

1 file changed

+4
-35
lines changed

1 file changed

+4
-35
lines changed

docs/Contributing.md

Lines changed: 4 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -45,45 +45,14 @@ To make code review easier, please consider manually porting the new hunks into
4545

4646
# Testing changes locally
4747

48-
```bash
49-
# First, create a new conda environment and add the conda-forge and robostack channels:
50-
51-
micromamba create -n robostackenv python=3.11
52-
53-
micromamba activate robostackenv
54-
micromamba config append channels conda-forge
55-
micromamba config append channels robostack-staging
56-
57-
# Install some dependencies
58-
micromamba install pip conda-build anaconda-client mamba conda catkin_pkg ruamel_yaml rosdistro empy networkx requests boa
59-
60-
# Install vinca
61-
pip install git+https://github.com/RoboStack/vinca.git --no-deps
62-
63-
# Clone the relevant repo
64-
git clone https://github.com/RoboStack/ros-humble.git # or: git clone https://github.com/RoboStack/ros-noetic.git
65-
66-
# Move in the newly cloned repo
67-
cd ros-humble # or: cd ros-noetic
48+
First of all, do the modifications in the `vinca_***.yaml` files for your platform, then run:
6849

69-
# Make a copy of the relevant vinca file
70-
cp vinca_linux_64.yaml vinca.yaml # replace with your platform as necessary
71-
72-
# Now modify vinca.yaml as you please, e.g. add new packages to be built
73-
code vinca.yaml
74-
75-
# Run vinca to generate the recipe; the recipes will be located in the `recipes` folder
76-
vinca --multiple
77-
78-
# Build the recipe using boa:
79-
boa build recipes -m ./.ci_support/conda_forge_pinnings.yaml -m ./conda_build_config.yaml
80-
81-
# You can also generate an azure pipeline locally, e.g.
82-
vinca-azure -d recipes -t mytriggerbranch -p linux-64
83-
# which will create a `linux.yml` file that contains the azure pipeline definition
50+
```bash
51+
pixi run build
8452
```
8553

8654
# How does it work?
55+
8756
- The `vinca.yaml` file specifies which packages should be built.
8857
- Add the desired package under `packages_select_by_deps`. This will automatically pull in all dependencies of that package, too.
8958
- The vinca.yaml files contain lots of commented-out package names. That is okay. Not all packages need to be rebuilt with every pull request. Do not be afraid if you see your package commented out after some time - it just means it is not being built now. For sure it will be built with next full rebuild. Full rebuilds happen occasionally (few times a year).

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy