On 13.01.2014 22:52, Simo Sorce wrote:
On Mon, 2014-01-13 at 22:43 +0100, Jakub Hrozek wrote:
> ACK to the approach especially considering the future work!
>
> I'm thinking about one aspect that might be just my personal
> preference
> so I'd like to hear other opinions. I'm completely addicted to
> cscope/ctags so I wonder how to make life easier for developers now
> that
> there are source files outside srcdir. Perhaps it would be enough to
> export $SOURCEDIRS (see man cscope) set to builddir in the bashrc_sssd
> script?
>
> I really don't have any comments about the code itself.
>
Ok I need to ask.
are we thinking of changing the code generators very often ?
Otherwise I would not mind having the autogenerated code committed to
the tree, and modified only when there is an actual change in the xml
file or the parsers.
This allows you to inspect changes to the generated code easily with git
diff too and also lets you find code with git grep, which I often use as
well, and would be very annoying if it failed to catch generated code.
This means generated code would stay in the srcdir and would not cause
issue with ctags/cscope either.
Not a bad idea.
It could cause frustration with folks trying to change the generated
code, and having it be overwritten etc. But I agree that's less
frustrating than constantly having to refer to $(builddir) to see part
of the code.
I'll do that.
Cheers,
Stef