-----Original Message----- >From: Tim Ellison <[EMAIL PROTECTED]> >Sent: Jan 4, 2006 6:46 AM >To: harmony-dev@incubator.apache.org >Subject: Re: repo layout again > >[EMAIL PROTECTED] wrote: >> >> Some more platform tree names: >> >> solaris32.sparc solaris64.sparc >> linux32.sparc linux64.sparc >> darwin32.ppc (Is this correct for the new MAC boxes?) > >Wouldn't the wordsize be better associated with the processor family? > >So solaris.sparc32, windows.x86, linux.ppc32, and so on.
Better yet, keep the three variables independent because the _same_ chip can operate in both a 32-bit and a 64-bit modes. It is the operating system that works in one mode or the other. Furthermore, a 64-bit OS also allows 32-bit applications to run on it in a compatibility mode. A good example of this is the Sun JDK that runs on Solaris. There is a 32-bit version, which is the default, and there is an additional 64-bit module that may be added on for running in 64-bit mode. The same SPARC processor is used for both. > >Maybe in some components we would want to include a window manager >family too, though let's cross that bridge... > >I had a quick hunt round for a recognized standard or convention for OS >and CPU family names, but it seems there are enough subtle differences >around that we should just define them for ourselves. > My VM's config script maintains CPU type, OS name, and word size as three independent values. These are combined in various ways in the source code and support scripts depending on the particular need. The distribution script names the 'tar' files for the binaries with all three as a part of the file name as, "...-CPU-OS-WORD.tar" as the tail end of the file name. (NB: I am going to simplify the distribution scripts shortly into a single script that creates the various pieces, binaries, source, and documentation. This will be out soon.) Does this help? Dan Lydick >Regards, >Tim > > >-- > >Tim Ellison ([EMAIL PROTECTED]) >IBM Java technology centre, UK. Dan Lydick
