Closed vs open builds

Magnus Ihse Bursie magnus.ihse.bursie at oracle.com
Mon Oct 21 06:51:44 UTC 2019


On 2019-10-19 12:24, Florian Weimer wrote:
> Is there a makefile flag to distinguish between closed
> (Oracle-internal/proprietary) and open builds?
Well, there is a configure option, --enable-openjdk-only, but it's a bit 
of an anachronism. The current idea is that we make closed builds by 
having the proper additional configure and makefiles present, which 
pulls them in.
>
> I want to fix some oversight in building the documentation (where
> content derived from open builds is incorrectly labeled as closed),
> and it would be nice to control the new behavior with such a flag.
Hm? I'm not sure what this means, but that sounds like a proper bug that 
should be fixed without reference to closed sources. If you have just 
OpenJDK checked out, with no closed sources present, the build should 
just create an open build without issues. Are you talking about the 
documentation in doc/*.md?

/Magnus



More information about the build-dev mailing list