ref: 997ea3e5ccd9cba5d1f8fad48a0320574696f5bc
parent: 503862f9000943b5cd72c1511828bae0c2050adc
author: Jacob Moody <[email protected]>
date: Wed Mar 29 14:48:47 EDT 2023
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.
--- a/sys/src/libc/port/mkfile
+++ b/sys/src/libc/port/mkfile
@@ -146,7 +146,7 @@
/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
@@ -153,3 +153,5 @@
$LD $LDFLAGS -o $O.mkrunetype mkrunetype.$O
$O.mkrunetype
}
+
+regen:V: runenormdata runetotypedata runeistypedata runebreakdata mkrunetype.c $UCD