Skip to content

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

Merged
khaledhosny merged 1 commit into
harfbuzz:masterfrom
Myaamori:master
Dec 1, 2020
Merged

meson: use meson.current_source_dir() instead of @CURRENT_SOURCE_DIR@#2755
khaledhosny merged 1 commit into
harfbuzz:masterfrom
Myaamori:master

Conversation

@Myaamori

Copy link
Copy Markdown
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

alerque commented Nov 24, 2020

Copy link
Copy Markdown
Member

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
Copy Markdown
Contributor Author

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

@CoffeeFlux

Copy link
Copy Markdown
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
@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.

4 participants