Chapter 1 System and Support Requirements

This chapter lists the requirements both for the host system where the sources are installed and maintained, and for the maintenance of the source code such that the source code can be supported. See the appropriate ChorusOS 5.0 Target Family Guide for details on standard board support packages.

This chapter in no way modifies or replaces any support contract you have concerning the source code, but instead provides instructions showing how you can maintain the source code you have licensed so that it is easier to patch and upgrade.

Host Requirements

The table below lists what must be provided in the host environment to support multiple source code versions for groups of software developers.

Table 1-1 Required Hardware and Software

Disk Space	50 Megabytes per version
Operating Environment	SolarisTM 7 Operating Environment (SPARCTM Platform Edition), with 32-bit and 64-bit support or SolarisTM 8 Operating Environment (SPARC Platform Edition), with 32-bit and 64-bit support, supporting symbolic links and long file names.
JavaTM support	JavaTM 2, Standard Edition, v 1.3, for the J2ME add-on package JDKTM v1.2 and upwards
Tools	ChorusOS operating system binary delivery installed for the appropriate target platform.  C/C++ compiler for the host, for SBA0 only gzip (provided in SUNWgzip) make (provided in SUNWsprot) Other tools: awk basename cat cc chmod cmp cp cut echo egrep find grep gzip head ln ls m4 mkdir mv rm sed sh sort sum tail test touch tr true uname uncompress uniq Source control tools such as the Source Code Control System (SCCS), to maintain the code base (not required, but highly recommended)

Developers working with the ChorusOS operating system also require separate disk space to work on their personal version of the ChorusOS source files.

Maintenance Requirements

Once installed, the ChorusOS source code base must be maintained in its original state so that you can apply official patches and upgrade it as improvements become available.

Code that you have modified must not be mixed with the original (patched) code. Mixing modified code with the original code might make it impossible to support your installation. If you need to modify one of the original files, you should first create a copy of the entire source component in a new directory. You can then use the configure command with the -s option referencing this new directory, rather than referencing the original component directory.

Follow these guidelines so you can continue to patch and upgrade the installed source code as development proceeds:

Use source control tools.

Tools that help you handle file histories, lock access to files being updated and merge differing versions of the same file play an indispensable role in allowing you to maintain ChorusOS operating system source code alongside the version you are using to develop your product. One such set of tools, the Source Code Control System, is bundled with the Solaris^TM operating environment but many other products exist.

Maintain the installed source code separately from all modified code.

Once you mix your modifications with the original source code, there is no guarantee that it remains possible to patch the code. Furthermore, your support contract might not extend to modifications that you introduced into the source code.

Decide which tool chain you will use for development.

The ChorusOS operating system source code delivery does not include the source code for the cross compiler and accompanying tools used on the host to develop software for the target system. Use the binary tools provided with the source version of the ChorusOS operating system.

Apply patches on the original code in the source installation directory, and then propagate the modifications.

Modifications should be propagated to source trees, and merged into your potentially modified copies. Patches are verified to work only on the original (patched) source code base. See Chapter 5, Patches for more information about patching.