From a3c0b515f9c39cbf0dc6ba9525ae2ea0a369ec5e Mon Sep 17 00:00:00 2001 From: Jehan Date: Thu, 22 Feb 2024 18:04:49 +0100 Subject: [PATCH] data: the build system should not ever move system files. AFAIU the issue which it tried to fix only happens on custom builds and it looks to me that it's just about multi-prefixes developer builds which were not configured with -Drelocatable-bundle=no as they should. When you compile GIMP yourself and intend to run it in a multi-prefix environment, without ever relocating the build, like on Unix-like systems, then disable this feature. In any case, we should never do this kind of system file moving hacks in our build system. The MSYS2 project even had to patch this out: https://gitlab.gnome.org/GNOME/gimp/-/merge_requests/1171#note_2022406 --- data/meson.build | 8 -------- 1 file changed, 8 deletions(-) diff --git a/data/meson.build b/data/meson.build index c9ff295a4d..159ebdcd96 100644 --- a/data/meson.build +++ b/data/meson.build @@ -26,11 +26,3 @@ configure_file( install: true, install_dir: gimpdatadir, ) - -# Fix iso-codes warning (Local-Native only) -if platform_windows and not meson.is_cross_build() - install_data( - join_paths(isocodes_location, 'iso_639.xml'), - install_dir: join_paths(get_option('datadir'), 'xml/iso-codes') -) -endif \ No newline at end of file