gingoduino/idf_component.yml at main · sauloverissimo/gingoduino · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
## ESP-IDF Component Manager manifest.
##
## Lets ESP-IDF projects pull gingoduino from the ESP Component Registry
## without vendoring src/ into the consumer tree:
##
##   # in your_app/main/idf_component.yml
##   dependencies:
##     sauloverissimo/gingoduino: ">=0.4.0"
##
## The Component Manager clones gingoduino into managed_components/, and
## ESP-IDF picks it up as a component because the top-level CMakeLists
## calls idf_component_register.

version: "0.6.0"
description: "Music theory engine for embedded systems. Notes, intervals, chords, scales, harmonic fields, harmonic trees, progression analysis, fretboard engine, real-time harmonic monitor, a live UMP stream interpreter (GingoFlow). Stateless output adapters serialize musical structures to MIDI 1.0 bytes and MIDI 2.0 UMP Flex Data."
url: "https://github.com/sauloverissimo/gingoduino"
repository: "https://github.com/sauloverissimo/gingoduino.git"
documentation: "https://github.com/sauloverissimo/gingoduino#readme"
issues: "https://github.com/sauloverissimo/gingoduino/issues"
license: "MIT"
maintainers:
  - "Saulo Verissimo <sauloverissimo@gmail.com>"
tags:
  - music
  - music-theory
  - midi
  - midi2
  - ump
  - flex-data
  - flow
  - chord
  - scale
  - harmonic-field
  - fretboard

targets:
  - esp32
  - esp32s2
  - esp32s3
  - esp32c3
  - esp32c6
  - esp32h2
  - esp32p4

dependencies:
  idf: ">=4.0"

## Exclude build artifacts and IDE configs from the published tarball.
files:
  exclude:
    - ".vscode/**/*"
    - ".git/**/*"
    - ".github/**/*"
    - "dist/**/*"
    - "bin/**/*"
    - "extras/tests/test_native"
    - "extras/tests/test_integration"
    - "extras/tests/vendor/**/*"