enlightenment/terminology
enlightenment
/
terminology
9
6
Fork 7
Code Issues 7 Pull Requests Projects Releases Wiki Activity
terminology/data/colorschemes/meson.build

47 lines
1.1 KiB
Meson
Raw Permalink Normal View History

generate colorschemes.eet
2020-09-13 14:39:34 -07:00
colorschemes_desc = [
colorschemes: add Belafonte Day/Night
2020-11-24 13:52:34 -08:00
'Belafonte Day.ini',
'Belafonte Night.ini',
colorschemes: add missing Black scheme
2021-01-30 02:37:57 -08:00
'Black.ini',
colorschemes: add Cobalt2
2020-11-26 13:50:09 -08:00
'Cobalt2.ini',
colorschemes: add Dracula
2020-11-22 14:19:17 -08:00
'Dracula.ini',
colorschemes: add Fahrenheit
2020-11-24 14:42:46 -08:00
'Fahrenheit.ini',
colorschemes: add Material
2020-11-24 14:22:21 -08:00
'Material.ini',
colorschemes: use ini instead of json
2020-10-07 14:48:04 -07:00
'Mild.ini',
'Mustang.ini',
'Nord.ini',
'Ocean Dark.ini',
colorschemes: add One Dark
2020-11-25 14:32:23 -08:00
'One Dark.ini',
colorschemes: add PaleNight theme
2020-11-25 14:09:44 -08:00
'PaleNight.ini',
colorschemes: use ini instead of json
2020-10-07 14:48:04 -07:00
'PaperColor.ini',
'Smyck.ini',
colorschemes: add Soft Era
2020-11-25 14:27:00 -08:00
'Soft Era.ini',
colorschemes: use ini instead of json
2020-10-07 14:48:04 -07:00
'Solarized.ini',
'Solarized Light.ini',
colorschemes: add the Tango {Dark,Light} colorschemes
2020-11-22 11:44:45 -08:00
'Tango Dark.ini',
'Tango Light.ini',
colorschemes: add Tomorrow Night Burns
2020-11-25 14:05:48 -08:00
'Tomorrow Night Burns.ini',
generate colorschemes.eet
2020-09-13 14:39:34 -07:00
]
Switch to using a color scheme per file. On Distro's we want to be able to ship color schemes as packages as such we need an easy way to add and remove them this commit implements the simplest possible solution of one color scheme per file.
2021-11-22 21:26:55 -08:00
colorschemes_out = []
foreach c : colorschemes_desc
colorschemes_out += c.replace('ini','eet')
endforeach
generate colorschemes.eet
2020-09-13 14:39:34 -07:00
cs_builder = [join_paths(meson.source_root(),
'data', 'colorschemes', 'builder.sh'),
Switch to using a color scheme per file. On Distro's we want to be able to ship color schemes as packages as such we need an easy way to add and remove them this commit implements the simplest possible solution of one color scheme per file.
2021-11-22 21:26:55 -08:00
eet_bin, '@INPUT@']
generate colorschemes.eet
2020-09-13 14:39:34 -07:00
cs_install_dir = join_paths(get_option('datadir'),
Switch to using a color scheme per file. On Distro's we want to be able to ship color schemes as packages as such we need an easy way to add and remove them this commit implements the simplest possible solution of one color scheme per file.
2021-11-22 21:26:55 -08:00
meson.project_name(),
'colorschemes')
generate colorschemes.eet
2020-09-13 14:39:34 -07:00
Switch to using a color scheme per file. On Distro's we want to be able to ship color schemes as packages as such we need an easy way to add and remove them this commit implements the simplest possible solution of one color scheme per file.
2021-11-22 21:26:55 -08:00
custom_target('colorschemes',
generate colorschemes.eet
2020-09-13 14:39:34 -07:00
install:true,
install_dir: cs_install_dir,
install_mode: 'rw-r--r--',
colorschemes: make it easier to add colorschemes
2020-11-22 02:43:05 -08:00
depend_files: ['builder.sh', 'ini2desc.py', 'get_name.py', 'add_color_scheme.sh'],
generate colorschemes.eet
2020-09-13 14:39:34 -07:00
command: cs_builder,
input: colorschemes_desc,
Switch to using a color scheme per file. On Distro's we want to be able to ship color schemes as packages as such we need an easy way to add and remove them this commit implements the simplest possible solution of one color scheme per file.
2021-11-22 21:26:55 -08:00
output: colorschemes_out)