Offhand: You would need to write the programs go generate is calling to be idempotent, and have the second one exit quietly if the first hasn't run. You would then either run go generate twice or have the first program run go generate once it had completed.
Not pretty but it does seem like a rare case. To be honest, I'd probably use a Makefile instead of go generate. -rob On Thu, Nov 10, 2016 at 2:37 AM, Paul Jolly <p...@myitcv.org.uk> wrote: > Hi - wondering whether anyone knows of any tooling that helps with > "pipelines" (probably not a great choice of phrase) of go generate-able > code. > > Specifically the case where the output of one go generate program is code > which is itself go generate-able (and hence requires another invocation of > go generate) > > There are various strategies I can think of for handling this situation, > but wanted to check if there was prior art out there before starting > something home-baked. > > Thanks, > > > Paul > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
