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: README.md
+14Lines changed: 14 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -169,6 +169,20 @@ listenPort=7767 ; exact same as [toolServer] coordinatorPort. make
169
169
```
170
170
Now you can stop WuildCoordinator and WuildToolServer on the client, and run both on the server (192.168.0.2) machine. Now you will have build distributed between two hosts.
171
171
172
+
# Configuration: commandline and config file
173
+
For every option in ini file, you can also provide its value form the commandline; you need to add ```--wuild-``` prefix to it, for example:
Any commandline option has higher priority that ini option. However, keep in mind, that all commandline variable placed in 'global' scope, so you can't provide different 'listenPort' for different scopes.
178
+
179
+
Let's now talk about ini config file location. It tries to load these locations in order:
180
+
-```--wuild-config=/path/file.ini``` command line parameter (and stops with error if path provided but invalid);
181
+
-```WUILD_CONFIG=/path/file.ini``` environment variable (and stops with error if path provided but invalid);
182
+
-```~/.Wuild/Wuild.ini``` (for Windows ~ is %USERPROFILE%);
183
+
- (Windows only) ```~/Wuild.ini```;
184
+
- Final attempt, it will try to load ```Wuild.ini``` in the same directory with main executable (e.g. WuildNinja).
185
+
If first two was not set and search is ended, then Wuild is set to "unconfigured mode". For WuildNinja it means it will fallback to plain ninja.
172
186
173
187
# Advanced usage
174
188
After Quick Start, next step is to add more ToolServers and maybe Coordinators (so you can safely shutown one server without disabling all builds on CI).
0 commit comments