EDIT :
Actually found out that once the request has parsed stdin it actually
contains the parameter so I will go for solution 2.1 if you have any
suggestions I'd still be glad to read them :)
Le jeudi 20 décembre 2018 14:44:49 UTC+1, Dregni Slovra a écrit :
>
> Hoï,
>
> I'm making a plugin for protoc to add some code at the end of an already
> built file of any language. My problem is in finding out what language to
> generate. At the moment, I found 2 solutions that works but aren't pretty
> and 2 solutions that doesn't quite work but looks better. I would like to
> know if one of the latest is possible and I missed something :
>
> So these works :
>
> 1. use theses flags : "--{language}_out=file --plugin_out=file
> --plugin_opt={language}" & base my generation off the option
> 2. use theses flags : "--{language}_out=file --plugin_out=file" & find
> the extensions of the files to figure out the language (haven't tried yet
> because it would be more pain than adding an option)
>
> and theses would be better to me but doesn't seem to work
>
> 1. use theses flags : "--plugin_out=file --plugin_opt={language}" &
> call {language}Generator from main depending on argv or something (which
> isn't set on anything but the plugin path)
> 2. use theses flags : "--plugin_out=file --plugin_opt={language}" &
> call {language}Generator from my plugin generate function but sets error
> to
> "{file}: Tried to write the same file twice."
>
> Thank you in advance !
>
--
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.
