PRE-COMPILED BINARIES OF NMM

These packages contain binaries of NMM. Each package is compiled with GCC 2.95.4 or GCC 3.3.1 on Debian woody GNU/Linux on a i686-computer.

What exactly does the package contain? The directory structure is as follows:

./bin            executables of the NMM examples and applications
./dev-lib        links to NMM plug-in libraries
./include        include files of NMM
./lib            all NMM libraries and external libraries
./resources      links to share/nmm
./share/doc      documentation for NMM
./share/nmm      images and configuration files for applications

Notice: The binary packages include most required libraries to use NMM and most of our applications, such as the Multimedia-Box and clic. Some libraries that should already be installed on most systems (like libltdl, libpng, libjpeg, libxml2, ...) are not included. Please install the corresponding packages of your GNU/Linux distribution. The binary packages do not replace a 'real' .deb or .rpm. They are not even assumed to work for all systems. You are free to compile NMM yourself.

1. Download NMM binary package
   The suffix of each archive specifies whether the package was compiled with GCC 2.95.4 or GCC 3.3.5. Run 'gcc --version' to check which version is installed on your system and download appropriate package.
   • NMM 0.9.1, compiled for systems with gcc 2.95.x and NMM 0.9.1, compiled for systems with gcc 3.x
   • Nightly binary Packages from sourceforge CVS: We offer nightly builds of our binary-packages created from the latest source code in the public Sourceforge CVS (compiled with GCC 2.95 and GCC 3.3.5). These packages can be used from developers or other users to get a precompiled NMM version that contains the latest changes and bugfixes. We recommend regular users to first try a binary package of an official NMM release, because the nightly binary packages might contain untested changes. All nightly binary packages can be accessed via our FTP server ftp://graphics.cs.uni-sb.de/www/NMM/dist/.
   
   
2. Extract the tar.gz package of release
   • 'cd /home/bob'
   • 'tar xvfz nmm-0.9.1-binaries-gcc2-i686.tar.gz' (will extract to /home/bob/nmm-0.9.1)
   
   
3. Set the environment variable NMM_DEV_DIR
   • 'export NMM_DEV_DIR=/home/bob/nmm-0.9.1' (for bash)
   • 'setenv NMM_DEV_DIR /home/bob/nmm-0.9.1' (for tcsh)
   
   
4. Set the environment variable LD_LIBRARY_PATH appropriately
   
   • 'export LD_LIBRARY_PATH=/home/bob/nmm-0.9.1/lib:$LD_LIBRARY_PATH' (for bash)
   • 'setenv LD_LIBRARY_PATH /home/bob/nmm-0.9.1/lib:$LD_LIBRARY_PATH' (for tcsh)
   
   

1. Set the environment variables NMM_DEV_DIR and LD_LIBRARY as described above
   • E.g. extend your personal ~/.tcshrc (for tcsh) or ~/.bashrc (for bash)
   
   
2. Setup NMM registry
   • Change to directory of NMM registry: 'cd /home/bob/nmm-0.9.1/bin/'
   • Run './serverregistry -s' and wait until all plug-in information is generated. Notice: This step is also performed automatically when you start some NMM application or example for the first time.
   
   
3. Test NMM
   • We recommend that you use 'clic' for testing NMM. clic is a very powerful tool.
   • Change to directory of clic: 'cd /home/bob/nmm-0.9.1/bin/'
   • Test audio: Run './clic gd/playback/audio/mp3play.gd -i <some mp3 file>'
   • Test video: Run './clic gd/playback/image/noise_yv12.gd' (You should see a window showing some video 'white noise' using the Xv extension.)
   • If clic does not work as expected, try adding '-v' for getting all error messages or '-vv' for all error and warning messages. Most often, the NMM_DEV_DIR or the LD_LIBRARY_PATH are not set correctly. Or, a plug-in required for the specific .gd file is not available. Repeat './serverregistry -s' and see, which plug-ins are available. Then compare this information with the content of the .gd file.
   • If everything works fine, you might want to read 'First steps with NMM'.
   
   
4. Setup Multimedia-Box
   • Copy /home/bob/nmm-0.9.1/resources/mmbox/mmboxrc_sample to your home as .mmboxrc and edit to fit your setup (see comments in mmboxrc_sample). There are only a few entries that you really have to edit; in many cases the default values are just fine. Notice: Since we frequently add new features to the Multimedia-Box, you should create a new .mmboxrc file for every new NMM release.
   • Change to directory of mmbox: 'cd /home/bob/nmm-0.9.1/bin/'
   • TV/EPG functionality: For all releases >= 0.9.1 you have to run './channelReader' before you are running the Multimedia-Box for the first time. This tool creates the global TV-Channel-Config-File '$HOME/.nmm/tv_channels.xml'. For more information, read Setting up LiveTV, TVGuide and TVTimer of the NMM Multimedia-Box [pdf]
   • Run './mmbox' or './mmbox --help'. In case the Multimedia-Box is not working as expected, use './mmbox -v' for getting all error messages or './mmbox -vv' for all error and warning messages.
   
   
5. Optional: Security
   • Copy /home/bob/nmm-0.9.1/resources/nmmrc_sample to your home as .nmmrc and edit it.
   • By setting 'allowedreadpaths' you can restrict the paths from which plug-ins are allowed to read data, e.g. your MP3 files.
   • By setting 'allowedwritepaths' you can restrict the paths to which plug-ins are allowed to write data.
   • By setting a 'passwd' you can restrict access between NMM processes (and therefore systems). Only processes using the same password are allowed to interact. For example, if you start a serverregistry on host A and another user at host B wants to connect to this serverregistry, both of you need to agree on the same password.
   • Notice: If you are behind a firewall and only connected to trusted hosts and users, you do not necessarily need these settings at all.
   • Notice: If you want to access devices, e.g. /dev/dsp for audio output, you need to add this to the 'allowed' paths. Remember: the usual restrictions of your operating system still apply, e.g. adding '/dev/' to 'allowedreadpaths' and 'allowedwritepaths' is not necessarily unsafe.