New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KeyError: 'install_dir' #9472
Comments
Sigh, yup. I'll get CustomTarget completely converted for 0.61... I might need to send out the gnome module cleanups piecemeal as they're rather draining to work on. |
The `mkenums` functions can have this unset if, and only if, the c file only variant is called. Due to side effects if the header file is generated then `install_dir` is ensured to be set for the c file. I have removed this side effect so that our tests actually cover this case. Fixes mesonbuild#9472
Wow, that's annoying. This can only be hit if you create only a c file, and don't pass an |
The `mkenums` functions can have this unset if, and only if, the c file only variant is called. Due to side effects if the header file is generated then `install_dir` is ensured to be set for the c file. I have removed this side effect so that our tests actually cover this case. Fixes mesonbuild#9472
The `mkenums` functions can have this unset if, and only if, the c file only variant is called. Due to side effects if the header file is generated then `install_dir` is ensured to be set for the c file. I have removed this side effect so that our tests actually cover this case. Fixes mesonbuild#9472
The `mkenums` functions can have this unset if, and only if, the c file only variant is called. Due to side effects if the header file is generated then `install_dir` is ensured to be set for the c file. I have removed this side effect so that our tests actually cover this case. Fixes mesonbuild#9472
The `mkenums` functions can have this unset if, and only if, the c file only variant is called. Due to side effects if the header file is generated then `install_dir` is ensured to be set for the c file. I have removed this side effect so that our tests actually cover this case. Fixes #9472
The `mkenums` functions can have this unset if, and only if, the c file only variant is called. Due to side effects if the header file is generated then `install_dir` is ensured to be set for the c file. I have removed this side effect so that our tests actually cover this case. Fixes #9472
The gnome.mkenums() function in Meson 0.60.0 doesn't work correctly if only the C file is generated and the install_dir argument is not provided. Work around the issue by always providing the argument, even when we know it's going to be ignored. mesonbuild/meson#9472 Signed-off-by: Andrea Bolognani <abologna@redhat.com>
some changes with this have broken gjs 1.70.0 build
this is a gnome.generate_gir invocation |
Fixed by #9667, which is in 0.60.3 |
Describe the bug
AUR package msitools fails to build with meson 0.60.0. The meson output looks like this:
According to #9365 (comment), it appears to be a meson bug that is not fully fixed.
To Reproduce
$ git clone https://aur.archlinux.org/msitools.git $ cd msitools/ $ makepkg
Expected behavior
The package builds without issue.
system parameters
meson --version
ninja --version
if it's a Ninja buildThe text was updated successfully, but these errors were encountered: