david.holmes at oracle.com
Tue Mar 6 17:56:16 PST 2012
On 7/03/2012 2:40 AM, Anthony Petrov wrote:
> Hi Martin,
> On 3/6/2012 6:17 PM, martin burtscher wrote:
>> if I use BUILD_HEADLESS=true the awt packages are included and
>> useable. So either I understand BUILD_HEADLESS wrong or it doesnt do
>> what its supposed to do.
> AWT can work w/o a display, e.g. for in-memory image manipulation, or
> printing support. So there's nothing wrong with having AWT packages
> built when the BUILD_HEADLESS is true.
Yep. BUILD_HEADLESS indicates to build headless support into the JDK.
Headful support is always present.
>> Second point is: Why do i need ALT_OPENWIN_HOME? I wanna build it
>> headless, so there's no use of X11. I removed the CROSS_COMPILE
>> options to test the headless build. (Just try to use the cross compile
>> to be sure its working before i use a different compiler...) btw:
>> changing ALT_OPENWIN_HOME doesnt change anything with the errors
>> (Xrender.h missing) i'll get when im using crosscompile.
> AFAIK, currently there's no an officially supported way to build an
> AWT-less OpenJDK.
Yes. The BUILD_HEADLESS_ONLY support was added for SE Embedded "legacy"
support for systems where you can't even compile the AWT code etc. But
even that no longer works correctly with the OpenJDK code base.
Martin: you would have to add ifndef BUILD_HEADLESS_ONLY in suitable
places to disable all AWT support in your build. I'm afraid I can't tell
you where all those places might be though.
> best regards,
More information about the build-dev