core-lightning/cln-grpc/Makefile

cln-grpc-wrongdir:
	$(MAKE) -C .. cln-grpc-all

CLN_GRPC_EXAMPLES :=
CLN_GRPC_GENALL = cln-grpc/proto/node.proto \
	cln-grpc/src/convert.rs \
	cln-grpc/src/server.rs

DEFAULT_TARGETS += $(CLN_GRPC_EXAMPLES) $(CLN_GRPC_GENALL)

$(CLN_GRPC_GENALL): $(JSON_SCHEMA)
	PYTHONPATH=contrib/msggen python3 contrib/msggen/msggen/__main__.py

cln-grpc-all: ${CLN_GRPC_GENALL} ${CLN_GRPC_EXAMPLES}
cln-grpc: Add generation of grpc protobuf file from schema 2022-01-14 19:45:30 +01:00			`cln-grpc-wrongdir:`
			`$(MAKE) -C .. cln-grpc-all`

			`CLN_GRPC_EXAMPLES :=`
cln-grpc: Add result conversion generator to `msggen` This takes the Rust bindings and converts them into the generated protobuf bindings: > JSON-RPC -> Rust bindings -> grpc bindings -> protobuf 2022-01-15 13:56:49 +01:00			`CLN_GRPC_GENALL = cln-grpc/proto/node.proto \`
cln-grpc: Generate server dispatcher The server doesn't do much more than unwrapping the request from its grpc envelope, convert it into the matching JSON-RPC binding struct, initiate the RPC connection (until we have connection pooling), and then forwards the converted request. The inverse then happens for the result. 2022-01-16 16:38:21 +01:00			`cln-grpc/src/convert.rs \`
			`cln-grpc/src/server.rs`
cln-grpc: Add result conversion generator to `msggen` This takes the Rust bindings and converts them into the generated protobuf bindings: > JSON-RPC -> Rust bindings -> grpc bindings -> protobuf 2022-01-15 13:56:49 +01:00
cln-grpc: Add generation of grpc protobuf file from schema 2022-01-14 19:45:30 +01:00			`DEFAULT_TARGETS += $(CLN_GRPC_EXAMPLES) $(CLN_GRPC_GENALL)`

			`$(CLN_GRPC_GENALL): $(JSON_SCHEMA)`
			`PYTHONPATH=contrib/msggen python3 contrib/msggen/msggen/__main__.py`

			`cln-grpc-all: ${CLN_GRPC_GENALL} ${CLN_GRPC_EXAMPLES}`