Skip to content
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

meson: use meson.current_source_dir() instead of @CURRENT_SOURCE_DIR@ #2755

Merged
merged 1 commit into from Dec 1, 2020

Conversation

Myaamori
Copy link
Contributor

@CURRENT_SOURCE_DIR@ is not listed as a valid string substitution for custom targets in the Meson reference, and in practice it does not get substituted when using the vs2019 backend.

@CURRENT_SOURCE_DIR@ is not listed as a valid string substitution
for custom targets in the Meson reference, and in practice
it does not get substituted when using the vs2019 backend.
@alerque
Copy link
Member

alerque commented Nov 24, 2020

This sounds right, but can we confirm from release docs when meson.current_source_dir() was added? Remember we're trying to keep supporting pretty old Meson versions here.

@Myaamori
Copy link
Contributor Author

It seems to have been present since version 0.14.0, hopefully that's old enough: mesonbuild/meson@9318203

@CoffeeFlux
Copy link
Contributor

Anything blocking a merge here? Would be great to get this in so we no longer have to work around it on our end.

@khaledhosny khaledhosny merged commit 07e304b into harfbuzz:master Dec 1, 2020
11 checks passed
@khaledhosny khaledhosny added the meson meson build system label Dec 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meson meson build system
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants