Building on Hardy Heron

From Gnash Project Wiki

Jump to: navigation, search

I thought I'd document the steps I took to build Gnash on Hardy Heron (currently Beta):

  • Don't do this build as root. Instead, do it as an ordinary user and use sudo to run things as root.
  • Check out Gnash from CVS.
CVSROOT=:pserver:anonymous@cvs.sv.gnu.org:/sources/gnash cvs co gnash
  • Oops, Hardy doesn't ship with cvs
sudo apt-get install cvs
  • Switch into the Gnash subdir.
cd gnash
  • First run autogen.sh to create configure.
sh autogen.sh
  • Oops, Hardy doesn't install autoconf or automake
sudo apt-get install autoconf automake
  • Try again
sh autogen.sh
  • Oops, libtoolize is missing.
sudo apt-get install libtool libltdl3-dev
  • Autogen now runs to completion
  • Now we run configure with the default arguments. It will complain about missing dependencies
./configure
  • Indeed, it did. Scroll up in the output and look for ERROR. We're only fixing the ERRORs now.
sudo apt-get install libboost-dev libboost-thread-dev libagg-dev libgstreamer0.10-dev libjpeg-dev libxml2-dev
  • For simplicity's sake, we'll leave off the kde gui, which is on by default.
./configure --enable-gui=gtk
  • We get new errors.
sudo apt-get install libboost-date-time-dev libatk1.0-dev libpango1.0-dev libgtk2.0-dev 
  • All errors gone; only warnings remain. Let's try compiling it.
make
  • Oops! configure didn't tell us that we don't have a C++ compiler, even though it works hard to find one. It would be nice if we could fix this. There's probably a way to do it, but people can figure out that if g++ is missing, they need to install g++. But, really, it's an autoconf problem.
sudo apt-get install g++
  • Now we run configure again so that it can properly detect g++.
./configure --enable-gui=gtk
  • and attempt a build.
make
  • and that successfully compiles!