Start X11 and web frontends for xC
For this, we needed a wire protocol. After surveying available options,
it was decided to implement an XDR-like protocol code generator
in portable AWK. It now has two backends, per each of:
- xF, the X11 frontend, is in C, and is meant to be the primary
user interface in the future.
- xP, the web frontend, relies on a protocol proxy written in Go,
and is meant for use on-the-go (no pun intended).
They are very much work-in-progress proofs of concept right now,
and the relay protocol is certain to change.
2022-08-08 04:39:20 +02:00
|
|
|
.POSIX:
|
|
|
|
.SUFFIXES:
|
2022-09-26 12:39:26 +02:00
|
|
|
AWK = env LC_ALL=C awk
|
Start X11 and web frontends for xC
For this, we needed a wire protocol. After surveying available options,
it was decided to implement an XDR-like protocol code generator
in portable AWK. It now has two backends, per each of:
- xF, the X11 frontend, is in C, and is meant to be the primary
user interface in the future.
- xP, the web frontend, relies on a protocol proxy written in Go,
and is meant for use on-the-go (no pun intended).
They are very much work-in-progress proofs of concept right now,
and the relay protocol is certain to change.
2022-08-08 04:39:20 +02:00
|
|
|
|
2022-09-30 03:23:06 +02:00
|
|
|
tools = ../liberty/tools
|
2022-09-15 22:45:14 +02:00
|
|
|
outputs = xP proto.go public/proto.js public/mithril.js
|
2022-09-22 18:57:14 +02:00
|
|
|
all: $(outputs) public/ircfmt.woff2
|
Start X11 and web frontends for xC
For this, we needed a wire protocol. After surveying available options,
it was decided to implement an XDR-like protocol code generator
in portable AWK. It now has two backends, per each of:
- xF, the X11 frontend, is in C, and is meant to be the primary
user interface in the future.
- xP, the web frontend, relies on a protocol proxy written in Go,
and is meant for use on-the-go (no pun intended).
They are very much work-in-progress proofs of concept right now,
and the relay protocol is certain to change.
2022-08-08 04:39:20 +02:00
|
|
|
|
|
|
|
xP: xP.go proto.go
|
|
|
|
go build -o $@
|
2022-09-30 03:23:06 +02:00
|
|
|
proto.go: $(tools)/lxdrgen.awk $(tools)/lxdrgen-go.awk ../xC.lxdr
|
|
|
|
$(AWK) -f $(tools)/lxdrgen.awk -f $(tools)/lxdrgen-go.awk \
|
|
|
|
-v PrefixCamel=Relay ../xC.lxdr > $@
|
|
|
|
public/proto.js: $(tools)/lxdrgen.awk $(tools)/lxdrgen-mjs.awk ../xC.lxdr
|
|
|
|
$(AWK) -f $(tools)/lxdrgen.awk -f $(tools)/lxdrgen-mjs.awk ../xC.lxdr > $@
|
2022-09-22 18:57:14 +02:00
|
|
|
public/ircfmt.woff2: gen-ircfmt.awk
|
2022-09-26 12:39:26 +02:00
|
|
|
$(AWK) -v Output=$@ -f gen-ircfmt.awk
|
Start X11 and web frontends for xC
For this, we needed a wire protocol. After surveying available options,
it was decided to implement an XDR-like protocol code generator
in portable AWK. It now has two backends, per each of:
- xF, the X11 frontend, is in C, and is meant to be the primary
user interface in the future.
- xP, the web frontend, relies on a protocol proxy written in Go,
and is meant for use on-the-go (no pun intended).
They are very much work-in-progress proofs of concept right now,
and the relay protocol is certain to change.
2022-08-08 04:39:20 +02:00
|
|
|
public/mithril.js:
|
|
|
|
curl -Lo $@ https://unpkg.com/mithril/mithril.js
|
|
|
|
clean:
|
|
|
|
rm -f $(outputs)
|