= Installation Notes = == Prepare the environment == You'll need: * A C++ compiler, preferably g++ * A working SystemC implementation * [http://www.systemc.org/ OSCI implementation] * SystemCass * Binutils and BFD for your target CPU, see CrossCompiler * A [http://subversion.tigris.org/ Subversion] client * A recent [http://www.python.org/ Python] interpreter * A bourne-shell compatible, like bash * [http://www.libsdl.org/ SDL] (for graphic utilities) == Getting SoCLib == If you haven't already done it, please register to create your account: {{{ #!html
}}} Please note that this e-mail will be your login ID. {{{ $ cd where/to/put/soclib $ svn co https://www.soclib.fr/svn/trunk/soclib soclib }}} Put `soclib/bin` in your `$PATH`, preferably add this line in your shell's startup scripts. {{{ $ export PATH=$PATH:where/to/put/soclib/bin }}} == Compiling tools == Some tools need compilation before use: {{{ $ cd where/to/put/soclib/utils/src $ make $ make install }}} == Configuration == === SystemC === You may edit [SoclibConf SoCLib's configuration file]. Out of the box, the only thing the configuration needs is setting an environment variable pointing to your SystemC implementation. Again this may preferably reside in your shell's startup scripts: {{{ $ export SYSTEMC=/path/to/systemc }}} If you want to check, you should have a listing close to this one: {{{ $ ls $SYSTEMC AUTHORS ChangeLog LICENSE README docs include COPYING INSTALL NEWS RELEASENOTES examples lib-linux }}} === Cross-compilation tools === By default, platform examples expect cross-toolchains compiled as described in CrossCompiler. I.e. it expects `mipsel-unknown-elf-gcc`, `powerpc-unknown-elf-gcc` and `mb-gcc` (Xilinx ships a Microblaze compiler named it this way). If you already have cross-toolchains compiled on your host, you can declare them in `~/.soclib/soft_compilers.conf`. For each architecture in `mipsel`, `powerpc` and `microblaze`, you may define: {{{