Basic Build Instructions

• Sun Java 1.6 or higher JDK
• Ant 1.7 or higher
• Perl 5.6 or higher
• gcc/g++ 3.2 or higher
• gmake 3.81 or higher
• Yasm 0.7 or higher
• pkg-config 0.26 or higher
• Internet Access. The first time you build Xuggler it will download some required .jar files using Ivy.
• Make sure you create a directory for $XUGGLE_HOME if you've defined it.

• mingw and msys with windows runtime 3.15.1 and gcc 4.2.4; other versions may not work
• Perl compiled for mingw and msys. ActiveState perl will not work.
• johnnie walker, 2 drinks or higher

• Get the most recent Apple development tools (Xcode 4.1 or later)

• Make sure that Xcode still has SDKs available at:

  /Developer/SDKs

  If not, it's likely because Xcode decided to move them. Make a soft link (change to where your Xcode is):

  sudo ln -s /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer /Developer

• Some OS X users have found that if the number of environment variables is fewer then 40, javac core dumps. A work around for this is to create a number of dummy environment variables before compiling Xuggler:

  for i in {1..40}; do export xuggler$i=foo; done

  Once Xuggler is installed, these dummy environment variables need not persist. Please pardon the voodoo.

• Some OS X users have found that adding /usr/local/lib to the DYLD_LIBRARY_PATH environment variable causes problems with a number of command line programs. $XUGGLE_HOME/lib/ will need to be added DYLD_LIBRARY_PATH and thus we advise against installing Xuggler directly into /usr/local.

• We have found that excuting sudo ant install will not get the RED5 environment settings. The following should ensure Xuggler installs into RED5.

  su root
  ant install
  exit

• On Mac, we build the 64 bit version by default (which seems to work with 1.6. It also works with Java 1.5 if you run Java in "-server" mode. If you need to force it to 32 bit (java 1.5 client mode), pass the following option on all ant calls:

  ant -Dconfigure.build.os=i386-apple-darwin

You can set XUGGLE_HOME to any directory you like, and if not set, we'll default to /usr/local (like most open source projects). You may want to use your own setting though to make it easier to add and remove, and to avoid overwriting any other installations of FFmpeg you may have.

export XUGGLE_HOME=/usr/local/xuggler
export PATH=$XUGGLE_HOME/bin:$PATH
export LD_LIBRARY_PATH=$XUGGLE_HOME/lib:$LD_LIBRARY_PATH

export XUGGLE_HOME=/usr/local/xuggler
export PATH=$XUGGLE_HOME/bin:$PATH
export DYLD_LIBRARY_PATH=$XUGGLE_HOME/lib:$DYLD_LIBRARY_PATH

Building on Windows is a big PITA. Alas, Windows doesn't have a nice command line way of setting variables, but using their GUI tool, set the following:

• Set XUGGLE_HOME to a directory of your choice (make sure the directory exists on disk). When building, you must make sure that your XUGGLE_HOME is on your C: drive, and is in a path with no spaces in it. Sorry. This restriction does not apply if you use the installer.
• Add %XUGGLE_HOME%\bin; to the start of your PATH environment variable.
• Optionally, set %XUGGLE_REPO% to a directory where you want ant to install published ivy jars (if you don't set it, it defaults to dist/ivy in your build directory).