<AWT Dev> xawt/libmawt.so and headless/libmawt.so

Alan Bateman Alan.Bateman at oracle.com
Wed Apr 20 06:10:55 PDT 2011

David Holmes wrote:
> :
> The only glitch I see with that is that the 
> GraphicsEnvironment.getHeadlessProperty code is Java code while to 
> check for the native lib we'd need native code.
The VM code is just stat'ing the library to check that it exists. It 
looks like we could do the equivalent in 
GraphicsEnvironment.getHeadlessProperty without needing any native code.
> It's doable I guess, but is it worthwhile? What problem are we trying 
> to solve?
In the modules build today then the JDK's native libraries still go into 
lib/<arch> but this may change so that a module's native libs go into 
the module's tree. Any re-organization or changes to the layout of 
native libraries is going to expose dependencies and other issues but 
hopefully that we can't overcome.


More information about the awt-dev mailing list