Re: [ANN] LuaAV OSX binary release

[Wesley Smith <wesley.hoke@...>]

> Are the individual modules generally usable in isolation (or in small
> sets)?  Some of those modules look tasty, but no way do I want a
> dependency on a huge "environment"...

The answer is yes with one caveat: most modules depend on the Array
module.  Any module that deals with buffers of data like images, video
frames, geometry buffers, need the Array module.  If you want to use
any of these modules, you'll have to have the Array module and its
corresponding header file so that the other modules have a definition
of Array.  The idea here is that we didn't want one large monolithic
module containing opengl, video, image, etc, so we designed a header
file with the definition of C/C++ objects for passing around memory
buffers and a lua module for manipulating them in scripts.  The
relevant files are:

http://www.mat.ucsb.edu/projects/luaAV/browser/trunk/dev/include/lua_array.h
http://www.mat.ucsb.edu/projects/luaAV/browser/trunk/libluaav/src/lua_array.cpp

There are some dependent headers but not that many.  If you want to
use them in your app, it should be pretty easy.  If there's something
that needs changing in order to make it work, we're happy to have any
patch submissions.

wes