From 3fca8936b29ff6d0eb48fdd9c31a03abc1ec49e0 Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Sat, 28 Dec 2019 00:24:15 +0000 Subject: [PATCH] README: Explain a wrinkle in &:include filename semantics Signed-off-by: Ian Jackson --- README | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/README b/README index c4f9d0e..b812f27 100644 --- a/README +++ b/README @@ -235,8 +235,11 @@ So pathname syntax is a subset of: &:include filename filename should usually be [&]foo.sd.mk &:-include filename tolerate nonexistent file - filenames are relative to $(top_srcdir) - RHS is &-expanded + RHS is &-expanded but filenames are relative to the top + srcdir. This implies that unqualified names are like &~/ + whereas &/ is like &^/. &^ and &~ do not work here because + they expand to constructions involving literally + `$(top_srcdir)', but the RHS is not make-expanded. &! disables & until EOL (and then disappears) -- 2.30.2