How to compile all proto files in a folder about cl-protobufs

[Slids]

It concatenates the resultants into a file.

Example:

I went to

jgodbou@penguin:~/quicklisp/local-projects/cl-protobufs/google/protobuf

Then I ran:

protoc --plugin=protoc-gen-lisp=/usr/local/bin/protoc-gen-lisp   --lisp_out=output-file=b.lisp:/tmp   --proto_path=.   a*.proto

If you look at b.lisp inside of /tmp we concatenate the different generated files.
Running cat /tmp/b.lisp | less you see:

;;; any.proto.lisp
;;;
;;; Generated by the protocol buffer compiler. DO NOT EDIT!

(cl:in-package #:common-lisp-user)

.
.
.

;;; api.proto.lisp
;;;
;;; Generated by the protocol buffer compiler. DO NOT EDIT!

(cl:in-package #:common-lisp-user)
.
.
.

[Slids]

I'd suggest sticking with ASDF and not bothering running protoc manually.

[Slids]

@mdbergmann did this sufficiently answer your question?

[mdbergmann]

Thanks for you answer.
Let me try this tonight.
I have a folder structure of .proto files so I'd be curious what it does with this. Or should protoc be called on a per folder basis?

What do you mean with 'sticking to ASDF'?

[Slids]

Once everything is installed, you can use
protobuf-source-file in your asd file.
It will call protoc for you.
Check the well-known-types module in the cl-protobufs asd for an example

cl-protobufs/cl-protobufs.asd

Line 73 in e0d0a27

(:module "well-known-types"

I guess this never made it to the readme?
Then that should be a documentation bug...

[mdbergmann]

Yeah, would be cool if that could get documented.