jdk/src/solaris - time to re-visit it?

Fredrik Öhrström fredrik.ohrstrom at oracle.com
Thu Nov 24 14:39:59 UTC 2011

2011-11-24 11:11, Alan Bateman skrev:
> The immediate benefit of renaming is that it would allow us to move the 
> Solaris and Linux specific source files out of the src/unix tree into 
> src/<platform> directories. That would eliminate the need for some of 
> the filtering in the build and would also allow us sort out some name 
> conflict issues that we have in several places 
> (UNIXProcess.java.<platform> for example).

It would be great to do the rename. However, we should not do that
before the build-infra changes
are in place. The peculiarities of the current build have already been
worked around and the new
makefiles are useful, since it is easy to see where the warts are.  Thus
when build-infra is done, we will
have a neat list of all things that needs to be cleaned up by moving
source code and platform
specific code in src/share is just one of many problems.

I was hoping that when we start incrementally moving towards jigsaw-like
structuring of the source,
we can fix this then? When we rename directories, we lose a lot of
information in the source control system.
Necessary yes, but at least we should try to do it just once.

As for the naming:
  posix is the name of a standardized API to unix-like operating systems.
  winapi is the name of the defacto API to windows systems.

Using two trademarks instead of the actual names of the APIs would be silly.

And you can run posix software on Windows by installing cygwin et al,
and you
can run winapi software on Linux by installing wine. But this is not the
the point is that the built jvm will run primarily using winapi, or
using posix.

No-one answered my question if we need to track the posix pedigree? I.e.
gnu, sysv and bsd?


More information about the build-dev mailing list