install.sc_ms

system c 是在C环境下的硬件描述语言,比VHDL 等语言具有更强的抽象能力,内有system C的开发支持库和一些VC下的开发例程

	INSTALL NOTES FOR systemc-2.0-MS2.0b3 Release 
	of Master/Slave Library
	------------------------------------------------

Contents:
	1. Installation Notes for Solaris 


1. Installation Notes for Solaris
---------------------------------

System Requirements
===================

SystemC can be installed on the following Solaris platforms

  1. Sun Solaris 2.7 and 2.8 with GNU C++ compiler version 2.95.2.

  Note : Versions for other platforms are under construction
  	 and will be made available in near future.


Sources for Compilers and Related Tools
=======================================

To build, install, and use SystemC on UNIX platforms, you need the
following tools:

  1. GNU C++ Compiler version 2.95.2,

  2. GNU Make (gmake)

GCC and gmake are free software that you can
obtain from the following sources:

  GCC		http://www.gnu.org/software/gcc/gcc.html

  gmake		http://www.gnu.org/software/make/make.html


Basic Master/Slave Installation
==========================

To install SystemC on a UNIX system, do the following steps:

  1. Change to the top level directory (systemc-2.0-MS2.0b3)

  2. Create a temporary directory, e.g.,

	> mkdir objdir

  3. Change to the temporary directory, e.g.,

	> cd objdir

  4. Set the following environment variable(s):

     For gcc-2.95.2 on Solaris:

	> setenv CXX g++


  5. Configure the package as follows :

	> ../configure --with-systemc-core=<path to SystemC core 2.0> 
	               --prefix=<path to SystemC core 2.0>


     e.g. ../configure 	--with-systemc-core=my_systemc_directory 
     			--prefix=my_systemc_directory

     Note : The --prefix should be the SAME as the path to systemc core.
	    
     While the 'configure' script is running, which takes a few moments, 
     it prints messages to inform you of the features it is checking.
     It also detects the platform.
     
     Note for System V users: 
     If you are using `csh' on an older version of System V, you might 
     need to use the `sh ../configure' command instead of '../configure'.
     Otherwise, `csh' will attempt to `configure' itself.

  . Compile the package.

     For an optimized master/slave library, enter:

	> gmake

     For a debug master/slave library, enter:

	> gmake debug

  7. Install the package.

	> gmake install

  8. You can now remove the temporary directory, .e.g,

	> cd ..
	> rm -rf objdir

     Alternatively, you can keep the temporary directory to later uninstall
     the package. To clean up the temporary directory, enter:

	> gmake clean

     To uninstall the package, enter:

	> gmake uninstall


Running the Examples
====================

1. Change to the example directory located under the directory
   where the master/slave library was installed 

   e.g. cd my_systemc_directory/examples/sc_ms/design_name

2. Read the brief description about the design in the README file. 

3. Build the example using `gmake' and corresponding Makefile for
   the platform :
   e.g. for solaris : gmake -f Makefile.gcc

4. Run the executable.
   run.x

Use the makefiles provided in  the 'examples' directory as templates for 
makefiles you need for compiling your own examples.
	
     
Using the Configure Script
==========================
 
The `configure' shell script tries to determine the correct values for
various system-dependent variables used during compilation. It uses
these values to create a `Makefile' in each directory of the package.
It also creates one or more `.h' files containing system-dependent
definitions if needed. Then, it creates the following files:

  config.status		A shell script that you can run at another time to
			recreate the current configuration.

  config.cache		A file in which the configure test results are
			saved to speed up reconfiguration.

			Data is appended to the config.cache file. 
			You can remove unwanted data.

  config.log		A file in which compiler output is saved.
			This is used to debug the configure script.

If you need to use other commands to successfully compile the package
on your system, please try to determine if the configure script can be used 
for these commands. Then, send either a diff file or instructions about
the commands you used to the email address provided in the README file.
This information will be used to improve the installation process in
the next release.

The `configure.in' file is provided in case you want to change or regenerate
the `configure' script, for example to use a newer version of `autoconf'. 
The `configure.in' file is used by the `autoconf' program to create the
`configure' script.

Note for (key) developers:

  In case you have changed the `configure.in' file or one of the
  `Makefile.am' files:

  - Use the `config/distclean' script to remove the generated `configure'
    script, the generated `aclocal.m4' file and the generated `Makefile.am'
    files.

  - Use the `config/bootstrap' script to generate the `configure' script
    and the necessary `Makefile.in' files. This script makes use of the
    GNU auto-tools `aclocal', `automake', and `autoconf'.


Compilation and Linking Options
===============================

Some systems require compilation or linking options that the `configure'
script does not define. You can define the initial values for these
options by setting them in your environment before running the
`configure' script.

Using a Bourne-compatible shell, the command line entry might be:

	> CC=c89 CFLAGS=-O2 LIBS=-lposix ../configure

Or, on systems that have the `env' program, the command line entry might be:

	> env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ../configure


Optional Features
=================

To build optimized libraries (default), from the top level directory run:

	> gmake opt

To build libraries with debug information, from the top level directory run:

	> gmake debug

followed by gmake, and gmake install.

e.g. the following command will rebuild the optimized library from scratch:

	> gmake clean opt install

By default, optimized libraries are built.


Specifying the System Type
==========================

Some features cannot be automatically determined by `configure' unless
it can detect the host type on which the package will run.
If it prints a message that it cannot determine the host type, 
use the `--host=TYPE' option to define it. TYPE can either be a 
short system name, such as `sun4', or a canonical name with three fields:

     CPU-COMPANY-SYSTEM

See the `config.sub' file for details about the values of each field. If
the `config.sub' file is not included in the package, the package does not
need to know the host type.

If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system for which
the code is produced and the `--build=TYPE' option to select the type of
system on which you are compiling the package.


Sharing Defaults
================

You can set the default values that `configure' scripts share by
creating a site shell script called `config.site'. This file contains the
default values for variables like `CC', `cache_file', and `prefix'.
The `configure' script looks for the `config.site' file in the following 
search precedence:

  1. PREFIX/share/config.site

  2. PREFIX/etc/config.site

Alternatively, you can set the `CONFIG_SITE' environment variable to the
site script path.

Note: The `configure' script for some systems does not look for a site script.


Operation Controls
==================

The `configure' script recognizes the following options to control its
operation:

`--cache-file=FILE'
	Use and save the test results in FILE instead of
	`./config.cache'. Set FILE to `/dev/null' to disable caching
	when debugging `configure'.

`--help'
	Print a summary of `configure' options and exit.

`--quiet'
`--silent'
`-q'
	Do not print messages about checks being made.
	To suppress all normal output, redirect it to `/dev/null'.
	Error messages continue to print.

`--srcdir=DIR'
	Look for the package's source code in directory DIR.
	Typically `configure' determines the directory automatically.

`--version'
	Print the version of `autoconf' used to generate the `configure'
	script and exit.

Other options that are rarely used are available in the `configure' script.
Use the `--help' option to print a list.