From 69a5c950a3a70fe2e31a8a35f0be51ded89c4937 Mon Sep 17 00:00:00 2001 From: Xavier Claessens Date: Wed, 7 Apr 2021 08:32:40 -0400 Subject: pkgconfig: Do not escape custom variables We need to escape space in variables that gets into cflags or libs because otherwise we cannot split compiler args when paths contains spaces. But custom variables are unlikely to be path that gets used in cflags/libs, and escaping them cause regression in GStreamer that use space as separator in a list variable. --- docs/markdown/snippets/pkgconfig_var_escaping.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 docs/markdown/snippets/pkgconfig_var_escaping.md (limited to 'docs/markdown/snippets') diff --git a/docs/markdown/snippets/pkgconfig_var_escaping.md b/docs/markdown/snippets/pkgconfig_var_escaping.md new file mode 100644 index 0000000..de0ee96 --- /dev/null +++ b/docs/markdown/snippets/pkgconfig_var_escaping.md @@ -0,0 +1,23 @@ +## Unescaped variables in pkgconfig files + +Spaces in variable values are escaped with `\`, this is required in the case the +value is a path that and is used in `cflags` or `libs` arguments. This was an +undocumented behaviour that caused issues in the case the variable is a space +separated list of items. + +For backward compatibility reasons this behaviour could not be changed, new +keyword arguments have thus been added: `unescaped_variables` and +`unescaped_uninstalled_variables`. + +```meson +pkg = import('pkgconfig') +... +pkg.generate(lib, + variables: { + 'mypath': '/path/with spaces/are/escaped', + }, + unescaped_variables: { + 'mylist': 'Hello World Is Not Escaped', + }, +) +``` -- cgit v1.1