CVS: packaging README-MAINTAINER.txt,NONE,1.1

Update of /cvsroot/mspgcc/packaging
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv15264

Added Files:
	README-MAINTAINER.txt 
Log Message:
readme for sysadmins, linux build


--- NEW FILE: README-MAINTAINER.txt ---
This readme is for mspgcc package maintainers and system admins that want
to install mspgcc from the sources.

mspgcc Linux howto
==================

The following steps get the files from mspgcc, and build the toolchain in a
working folder and install them to /opt/mspgcc. If a different installation
directory is desired, it can be edited in the ``makefile``.

The installation directory has to be writable by the user that runs ``make``.
This is because the build/installation is made in steps and each step depends
on the previous one. This also means that ``make build`` is installing on the
fly, there is no separate ``make install``.

Preparation of the installation directory. Run these commands as root.
``$USER`` shoud be replaced with the login name of the user that build the
toolchain with the commands below::

    mkdir -p /opt/mspgcc
    chwown $USER.$USER /opt/mspgcc

The toolchain can now be built as ordinary user::

    mkdir -p mspgcc/sf
    cd mspgcc/sf
    cvs -d:pserver:[email protected]:/cvsroot/mspgcc login
    cvs -z3 -d:pserver:[email protected]:/cvsroot/mspgcc co -P .
    cd packaging
    make folders
    make build

.. note:: It may be required to use gcc-3.4 (or older) to cross compile
          gcc-3.2.3. gcc-4.0 may not work. In that case use  e.g.
          ``CC=gcc-3.4 make build`` as the last line for the commands shown
          above.

If you want to use ``msp430-jtag``, ensure that ``/dev/parport0`` is available::

    modprobe ppdev

And that the user is in the group with access to the device::

    addgroup $USER lp         # new login required to take effect

A line containing "ppdev" can be added to ``/etc/modules``, so that the
module is automaticaly loaded on startup.

Append line in ``/etc/environment``, so that the commands of the toolchain
are found::

    PATH=$PATH:/opt/mspgcc/bin


mspgcc Windows howto
====================
Ordinary users of the toolchain should download the installer from the
http://mspgcc.sf.net.

The makefile supports building the installer. ``make build-installer`` should
take care of everything, given that cygwin, python (with ctypes and py2exe)
and NSIS are installed and available on the ``PATH``.

Notes
=====

- The ``makefile`` contains individual targets to download, build and install
  the parts, like ``binutils-build``, ``binutils-install``. This can be used to
  rebuild only one part without recompiling everything else.
  
- To make the parts selectable in the windows installer, file lists are required.
  These are generated by comparing files before/after installing. 

  .. note:: To build the final windows installer, all installation steps have
            to be performed excatly once, or the file lists will be wrong.
            This is the case if the installer is built in one step like
            described above. Otherwise ``make clean-installdir install-only``
            should take care of this. It simply installs everything again,
            starting form an empty folder.

- The configure and compiler outputs are sent to log files located in the
  ``build`` subfolder. It may be needed to look at them in case of errors.

- ``make debug`` shows the values of a few internal variables that are used
  for the build, like the installation directory, etc.

- To build different versions of the various tools, the makefile has to be
  edited.

- The ``build`` subfolder can be deleted after successful installation. It
  takes away a few hundred megabytes of diskspace.



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl