Darren J Moffat writes: > James C. McPherson wrote: > > Javen Wu wrote: > >> Hi folks, > >> > >> Do you know whether the onbld tool chain and war lock are opened > >> opensolaris or not? > >> I am not sure how can make 3rd party vendor's code conform to Sun's > >> cstyle, comments standard and so on. > >> It's appreciated if you have any information. > > > > > > Hi Javen, > > yes, the onbld tools are open. Outside of Sun people can > > get them from > > > > http://www.opensolaris.org/os/project/scm-migration/ > > > > http://dlc.sun.com/osol/scm/SUNWonbld/SUNWonbld-latest.i386.tar.bz2 > > http://dlc.sun.com/osol/scm/SUNWonbld/SUNWonbld-latest.sparc.tar.bz2 > > and the source code for them is in the ON consolidation under usr/src/tools.
It wasn't clear to me if the original poster was just asking about SUNWonbld or if he was referring to the whole tool chain -- which includes the Sun C compiler and related tools. Those other things aren't open source. As for the C Style and other standards, the answers vary depending on exactly what you're trying to do, and how you hope to accomplish it. In general, for source code that's actively kept in sync with some external respository, and that merely has a different style (not a plainly _horrible_ one ;-}), it's common to keep the source files as close to the original as possible to minimize upgrade pain. You'll need to explain this to your RTI Advocate. Note that the Makefiles (at least in ON) must conform to ON's standards. You may need to write those from scratch. For source that won't be kept in sync, because we're forking, or because the original was just too much of a mess to contemplate supporting, I'd advise just going whole-hog: convert it to ON. It's a choice you have to make and defend. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
