Alan,
It's definitely tricky (lots of refactoring needed) but it definitely
needs to be done at some point - however I think we already missed the
opportunity to do this before integrating the BSD and MacOSX code (same
on the VM side)
David
On 23/11/2011 10:12 PM, Alan Bateman wrote:
In t
Its tricky.
I would not gratuitously change any of the directory names, especially
the win32 one.
There'd have to be a compelling reason.
The Linux and Solaris ports share X11 for their windowing system, but
the OS X port
doesn't. So some mac things would go in src/solaris, as they are
shar
On 23/11/2011 13:33, Fredrik Öhrström wrote:
:
I have no suprise there I guess ;-). If you read
CompileJavaClasses.gmk in build-infra/jdk7/jdk/make
you can see the hoops we need to go through to filter out platform
specific classes in share/classes
and linux specific classes in solaris/classe
At the risk of including Yet Another alias, you should include
[email protected], for the team working on the new build
system.
-- Jon
On 11/23/2011 06:40 AM, Dmitry Samersoff wrote:
Alan,
I'd thought about it couple of times (actually, every time i touched
networking code)
U
Alan,
I'd thought about it couple of times (actually, every time i touched
networking code)
Unfortunately there is no simple solution because lots of code has huge
common part and small platform specific function on top of it.
Also with a course to expand platform coverage it's possible to end u
2011-11-23 13:12, Alan Bateman skrev:
> In the jdk repository then src/solaris has all the Solaris and Linux
> code. Most of it is used for both platforms with a small number of files
> specific to one or the other. I'm sure this has come up before (probably
> many times) but I'd like to bring i
In the jdk repository then src/solaris has all the Solaris and Linux
code. Most of it is used for both platforms with a small number of files
specific to one or the other. I'm sure this has come up before (probably
many times) but I'd like to bring it up again.
One of motives for bringing th
