NLS files created in srcdir not in objdir

[Mark Mitchell]

>>>>> "Philipp" == Philipp Thomas <pthomas@suse.de> writes:

    Philipp> Jeff, Mark,

    Philipp> I wasn't sure to whom of you two I should address this,
    Philipp> so I took the easy road and included both of you :) A
    Philipp> word of clarification as to whom I should direct such
    Philipp> questions in the future would be nice, though I guess
    Philipp> Mark is the one, ain't it?

It's true that some time pretty soon it'll probably be my head on the
block.  But Jeff's long-standing experience is going to mean that his
opinion will carry a lot of weight with me.  And, as always, the SC
always has final say.

    Philipp> Currently all NLS files generated, i.e. gcc.pot and the
    Philipp> .mo/.gmo files are created in the srcdir. This makes it
    Philipp> impossible to have srcdir mounted ro (e.g. via NFS) when
    Philipp> configured with --enable-nls. I believe this to be a bug
    Philipp> and if you agree, I'll try to come up with a patch that
    Philipp> creates those files in objdir.

I think that the policy should be that files that are the same, no
matter what target you're building, should go in the srcdir.  Other
things should go in the objdir.  I don't know which category the NLS
stuff falls into.  But, for example, the `parse.c' files are currently
put in the srcdir, and that prevents read-only mounting there, too.  I
think that's the right tradeoff -- it makes it easier to build more
than one target from the same source tree.

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com