7179349 misses updating new build makefiles

[Kelly O'Hair]

Checking in generated files is never a good idea when it can be avoided.
It just creates a long term maintenance issue and can create legal issues depending on what the generated file is.

I'm open to ideas here, I don't like the current situation, but I'd rather have it this way than to check in a
generated file. This is not generated java code, but generated native code.

-kto

On Oct 24, 2012, at 7:41 AM, Magnus Ihse Bursie wrote:

> On 2012-10-24 00:20, Mike Duigou wrote:
>> How so? It's a MacOS specific dependency and always present there. (at least since 10.4)
> Well, in that case it sounds good. In principle I think the current explosion of small build tools is, eh, not so good.
> 
> On the other hand, most of these small build tools keep re-generating the very same stuff with identical result over and over again, since it's based on some not-very-often-changing source. I think it would be more efficient to check in the source code that these tools generate, and then have a special target "update-generated-sources" that will run these tools. This tool would only have to be run every now and then, and the generated java source code could be compiled with the normal code, making it possible to start java compilation directly when building the jdk target.
> 
> /Magnus