FYI, I have used the protoc tool myself in the past. If you get it working well, I would like to see this tool make it into the regular distribution.
I'm not sure the process has a strict guideline atm, but the idea would be to add it to the new contrib repo https://bitbucket.org/scons/scons-contrib and once its considered stable, merge it into the baseline. Food for thought, William On Mon, May 9, 2016 at 9:22 PM, William Blevins <wblevins...@gmail.com> wrote: > Very welcome. > > For future reference, this issue should really have gone to the users-list > instead :) > > V/R, > William > > On Mon, May 9, 2016 at 8:58 PM, Schleimer, Ben via Scons-dev < > scons-dev@scons.org> wrote: > >> > Also, if you are talking about getting implicit dependencies and >> cross-language dependencies, then you need version 2.5.0+ >> >> >> Ah, thank you. I missed that in the release notes. I'm running with 2.4.1 >> right now. I'll checkout 2.5 then... >> >> > >> >The emitter should only return the outputs of the protoc call, so java, >> cpp, or python files, correct? The emitter isn't supposed to output (for >> example) the java class files; thus, I don't know why you would run the >> scanner at all. >> >> >> Yeah, thats what I thought. Thank you... >> _______________________________________________ >> Scons-dev mailing list >> Scons-dev@scons.org >> https://pairlist2.pair.net/mailman/listinfo/scons-dev >> > >
_______________________________________________ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev