Changes between Initial Version and Version 1 of Installation Notes


Ignore:
Timestamp:
Mar 27, 2007, 5:39:07 PM (17 years ago)
Author:
Nicolas Pouillon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Installation Notes

    v1 v1  
     1= Installation Notes =
     2
     3== Prepare the environment ==
     4
     5You'll need:
     6 * A C++ compiler, preferably g++
     7 * A working SystemC implementation
     8   * [http://www.systemc.org/ OSCI implementation]
     9   * SystemCass
     10 * Binutils and BFD for your target CPU
     11 * A [http://subversion.tigris.org/ Subversion] client
     12 * A recent [http://www.python.org/ Python] interpreter
     13 * A bourne-shell compatible, like bash
     14 * [http://www.libsdl.org/ SDL] (for graphic utilities)
     15
     16== Getting SoCLib ==
     17
     18{{{
     19$ cd where/to/put/soclib
     20$ svn co https://www.soclib.fr/svn/trunk/soclib soclib
     21}}}
     22
     23Put `soclib/bin` in your `$PATH`, preferably add this line in your shell's startup scripts.
     24
     25{{{
     26$ export PATH=$PATH:where/to/put/soclib/bin
     27}}}
     28
     29== Compiling tools ==
     30
     31Some tools need compilation before use:
     32{{{
     33$ cd where/to/put/soclib/utils/src
     34$ make
     35$ make install
     36}}}
     37
     38== Configuration ==
     39
     40You may edit [SoclibConf SoCLib's configuration file]. Out of the box, the only thing the configuration
     41needs is setting an environment variable pointing to your SystemC implementation. Again
     42this may preferably reside in your shell's startup scripts:
     43{{{
     44$ export SYSTEMC=/path/to/systemc
     45}}}
     46
     47If you want to check, you should have a listing close to this one:
     48{{{
     49$ ls $SYSTEMC
     50AUTHORS  ChangeLog  LICENSE  README        docs      include
     51COPYING  INSTALL    NEWS     RELEASENOTES  examples  lib-linux
     52}}}
     53
     54== Other paths ==
     55
     56You should have cross-compilers in you path as well.
     57For instance you should have a generic mipsel compiler toolsuite available as
     58`mipsel-unknown-elf-*`.
     59
     60If they are not in the `$PATH`, add them in:
     61{{{
     62$ export PATH=$PATH:/path/to/compiler/suite/bin
     63}}}
     64
     65== Testing ==
     66
     67Let's compile a simple platform:
     68{{{
     69$ cd /path/to/soclib/platforms/timer_4mips
     70$ make
     71[...]
     72$ ./system.x
     73}}}
     74
     75If ever this fails, see if [SoclibConf SoCLib's configuration file] may help you.