summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJacob Moody <moody@posixcafe.org>2023-03-29 18:48:47 +0000
committerJacob Moody <moody@posixcafe.org>2023-03-29 18:48:47 +0000
commit997ea3e5ccd9cba5d1f8fad48a0320574696f5bc (patch)
tree1e54b4bb8dc641ca700534edb32d9ae06d3d888d
parent503862f9000943b5cd72c1511828bae0c2050adc (diff)
libc: runecomp: move generated files to explicit regen rule
While a previous commit attempted to address the issues of a ; cd /sys/src/ && mk nuke && mk install it seems that any kind of automatic detection for when to rebuild will blow up in someones face. I am moving this to an explicit virtual rule, the generated files are expected to be there.
-rw-r--r--sys/src/libc/port/mkfile4
1 files changed, 3 insertions, 1 deletions
diff --git a/sys/src/libc/port/mkfile b/sys/src/libc/port/mkfile
index 3388f7551..557f1d7fa 100644
--- a/sys/src/libc/port/mkfile
+++ b/sys/src/libc/port/mkfile
@@ -146,10 +146,12 @@ UCD=\
/lib/ucd/%:
cd /lib/ucd && mk $stem
-runenormdata runetotypedata runeistypedata runebreakdata: mkrunetype.c $UCD
+runenormdata runetotypedata runeistypedata runebreakdata:
@{
eval `{grep '^[A-Z]' /$cputype/mkfile}
$CC $CFLAGS -o mkrunetype.$O mkrunetype.c
$LD $LDFLAGS -o $O.mkrunetype mkrunetype.$O
$O.mkrunetype
}
+
+regen:V: runenormdata runetotypedata runeistypedata runebreakdata mkrunetype.c $UCD