mirror of https://github.com/GNOME/gimp.git
52928e04a5
This is untested on my side, because the bug only happens on native
builds with meson (our CI has cross-builds with meson and native builds
with autotools and I only do cross-builds locally) but I think/hope it
will work.
Basically we were using .full_path() because these rc files were also
used as input of some configure_file() calls which doesn't like custom
target objects as input (it wants strings or file objects). Yet a bug
in meson didn't like the colon used in native Windows full paths ('C:'
and such) when used in windows.compile_resources(). This has been fixed
by Luca Bacci in: https://github.com/mesonbuild/meson/pull/9368
Yet we just cannot depend on very early meson (or worse dev meson code).
On the other hand, if the input is a custom_tgt object, it uses the
object ID which we give as first parameter of custom_target() so we know
it's appropriately named without colons (such as 'gimp_plugins_rc').
Thus we should not bump into this issue again.
For the few usage in configure_file(), I just add a .full_path() only
when needed at call time.
Last but not least, I replace the bogus `meson --version` call by a
`python3 -c 'exit()'` as advised by Eli Schwartz:
|
||
|---|---|---|
| .. | ||
| .gitignore | ||
| Makefile.am | ||
| file-darktable-export-on-exit.lua | ||
| file-darktable-get-size.lua | ||
| file-darktable.c | ||
| file-raw-formats.h | ||
| file-raw-placeholder.c | ||
| file-raw-utils.c | ||
| file-raw-utils.h | ||
| file-rawtherapee.c | ||
| meson.build | ||