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/gettingstarted/installing.md
+31-33Lines changed: 31 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,41 +56,51 @@ See the [Troubleshooting](../troubleshooting/README.md) section for debugging ti
56
56
57
57
## Use your local software installations
58
58
59
-
You will not find the packages you have built immediately available on your shell: we provide a tool
60
-
called `alienv` that configures your shell according to the packages you want to load.`alienv` is
61
-
capable of switching between different versions of the same package without a hassle.
59
+
You will not find the packages you have built immediately available on your shell.
60
+
We provide a tool called `alienv` that configures your shell according to the packages you want to load.
61
+
`alienv` is capable of switching between different versions of the same package without a hassle.
62
62
63
-
**List your available packages with:**
63
+
Load the latest O2Physics version you have built.
64
64
65
65
```bash
66
-
alienv q
66
+
alienv enter O2Physics/latest
67
67
```
68
68
69
-
**Load the latest version you have built of a package (O2Physics for instance):**
69
+
The `alienv enter` command drops you to a new shell with the O2Physics environment. Unload the packages by simply exiting the environment with
70
+
the `exit` command.
70
71
71
-
```bash
72
-
alienv enter O2Physics/latest
72
+
```warning
73
+
Dependencies are loaded automatically. Do not attempt to load O2 or ROOT as well! You will find them automatically in the environment. `alienv enter` is verbose and will inform you about the loaded packages.
73
74
```
74
75
75
-
_⚠️ Dependencies are loaded automatically. Do not attempt to load O2 or ROOT as well, you will
76
-
find them automatically in the environment! `alienv enter` is verbose and will inform you about the
77
-
loaded packages if you have doubts._
76
+
```tip
77
+
If you have built several Git branches of O2Physics, you can enter the environment of a given branch `[branch]` with `alienv enter O2Physics/latest-[branch]-o2`.
78
78
79
-
The `alienv enter` command drops you to a new shell. Unload the packages by simply exiting it with
80
-
the `exit` command.
79
+
You can list all your available packages with `alienv q`.
80
+
```
81
81
82
82
## Building partially for development using ninja
83
83
84
-
This requires that the O2Physics build succeeded. Enter the environment as explained in the previous step specifying in addition the ninja package:
84
+
```note
85
+
This requires that you have successfully built Git branch `[branch]` (e.g. `master`) of O2Physics with aliBuild (see Section [Build and rebuild](#build-and-rebuild)).
86
+
87
+
You also need to have [`direnv`](https://direnv.net/docs/installation.html) installed to load the correct build environment automatically when you enter the build directory (and to unload it when you exit).
88
+
```
89
+
90
+
```warning
91
+
This only builds O2Physics. If you have updated O2 or alidist, you first need to do a full build with aliBuild.
@@ -123,18 +129,10 @@ A specific executable can be built in the staging directory `stage/bin` with
123
129
ninja stage/bin/<target>
124
130
```
125
131
126
-
For example:
127
-
128
-
```bash
129
-
ninja stage/bin/o2-analysis-cf-correlations
130
-
```
132
+
For example: `ninja stage/bin/o2-analysis-cf-correlations`
131
133
132
134
The executable can then be executed directly from the staging directory:
133
135
134
136
```bash
135
-
./stage/bin/o2-analysis-cf-correlations
136
-
```
137
-
138
-
```danger
139
-
This only builds O2Physics. If you have updated O2 or alidist, you first need to do a full build with aliBuild. Then enter the environment again before using ninja.
0 commit comments