On May 18, 2009, at 4:46 PM, Ulrich Hertlein wrote: > G'day! > > libavg has been on my radar for quite a while but I never had the > need to actually do something with it. Until recently that is :-D > > Since I expect to do some coding in the engine itself I went for the > svn route. > And since most of the dependencies are already installed via > MacPorts so I thought I'd try to make it work with that instead of > installing separate binaries for that.
Ok, nice. I tried that 2 or 3 years ago and failed because the MacPorts packages weren't really very good at that time. > Here are my experiences with that for future reference: > - the documentation on libavg.de is out of date (e.g. it mentiones > CVS) Oops. I've added a bug to the tracker. https://www.libavg.de/wiki/index.php/Libavg_on_Mac_OS_X is up-to-date, though :-). > - the 'bootstrap' script uses a toolchain from a relative directory > that doesn't exist on my system. Rewriting the script to use > 'glibtoolize' (from MacPorts, but Apple also has it in /usr/bin/ > glibtoolize) works just fine. Yes, the bootstrap script is meant for installing without external packages. The toolchain is included in http://www.libavg.de/macdependencies.tar.bz2 . > - (glibtoolize stands for 'GNU libtoolize' not 'glib toolize'; it's > been renamed to avoid conflict with Apple's libtool) > - to pick up boost_python and boost_thread libraries I had to run > configure with the following options: > LDFLAGS=-L/opt/local/lib BOOST_PYTHON_LIBS=-lboost_python-mt ./ > configure --prefix=/usr/local > - MacPort currently includes ffmpeg 0.5 which complained about one > argument to sws_getContext being int rather than PixelFormat Thanks :-). I've comitted that. > - TextEngine looks for fonts.conf in /etc/fonts and (if that fails) > in <libpath>/etc/fonts/fonts.conf; I've modified it so that it looks > in /etc/fonts, /usr/local/etc/fonts, /opt/local/etc/fonts (the > MacPorts location), and finally in getAvgLibPath()/etc/fonts; the > search paths could be modified for different environments (Linux, > Windows, OS X) I think we need a line in avgrc for this... > I've attached the modified files. Please use svn diff the next time. Figuring out what baseline you used becomes hard otherwise. Cheers, Uli -- Any technology distinguishable from magic is insufficiently advanced. Ulrich von Zadow | +49-172-7872715 Jabber: [email protected] Skype: uzadow _______________________________________________ libavg-users mailing list [email protected] https://mail.datenhain.de/mailman/listinfo/libavg-users
