Skip to content
Snippets Groups Projects
Commit 7dcac4a4 authored by Filippo Cremonese's avatar Filippo Cremonese
Browse files

Lowercase Orchestra -> orchestra

parent 2639cccb
No related branches found
No related tags found
No related merge requests found
......@@ -11,8 +11,8 @@ add_to_path:
- $ORCHESTRA_DOTDIR/support
environment:
- JOBS: #@ str(data.values.parallelism)
#! TODO: maybe patching RPATH should not be a concern of Orchestra itself, but rather a post-install phase
#! Otherwise, it should be Orchestra to provide an RPATH_PLACEHOLDER, not the other way around
#! TODO: maybe patching RPATH should not be a concern of orchestra itself, but rather a post-install phase
#! Otherwise, it should be orchestra to provide an RPATH_PLACEHOLDER, not the other way around
- RPATH_PLACEHOLDER: #@ options["rpath_placeholder"]
- QML2_IMPORT_PATH: $ORCHESTRA_ROOT/qml
- QT_PLUGIN_PATH: $ORCHESTRA_ROOT/plugins
......
......@@ -21,7 +21,7 @@
#@yaml/text-templated-strings
---
#@ def _configure_base(extra_qmake_args=[]):
#! TODO: In legacy Orchestra QMAKE_RPATHDIR has +="" in debug and release but ="" in optimized. Is it intentional?
#! TODO: In legacy orchestra QMAKE_RPATHDIR has +="" in debug and release but ="" in optimized. Is it intentional?
- |
mkdir -p "$BUILD_DIR"
cd "$BUILD_DIR";
......
# rev.ng Orchestra config
# rev.ng orchestra config
This repository contains the Orchestra configuration for rev.ng.
This repository contains the orchestra configuration for rev.ng.
To get started:
* install Orchestra (follow the instructions in its repo)
* install orchestra (follow the instructions in its repo)
* run `orchestra components` to generate the default user configuration
* edit `.orchestra/config/user_remotes.yml` to add your remotes, like so:
```
......
# Writing a component
This document explains the conventions used in this configuration.
Before reading it you should read Orchestra documentation
and understand the configuration format used by Orchestra.
Before reading it you should read orchestra documentation
and understand the configuration format used by orchestra.
TL;DR: an Orchestra configuration is a collection of **components** and other options.
TL;DR: an orchestra configuration is a collection of **components** and other options.
Components consist mainly of a collection of builds.
```yaml
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment