Sorry for the exasperated message earlier. Here is some more concrete information on my progress.
I have gotten all of the dependencies installed using standard released packages. At this point, I realized that pigment was compiling against a different glib/gtk build and would not be compatible with the glib/gtk/gstreamer versions required by the standard python bindings. So now in order to get a compatible set of binaries my options are 1) compile the glib/gtk/gstreamer python bindings against the OABuild version of glib/gtk/gstreamer or 2) compile pigment against standard released builds of glib/gtk/gstreamer. I cannot really wrap my head around the magic that is performed by OABuild enough to create a similar build environment for the glib/gtk/gstreamer bindings, so my inclination would be to go with option 2. Judging by the versions of glib/gtk/gstreamer binaries shipped with elisa, it is clear that you chose option 1. What is the reason for this? Is there a chance that your build files for the glib/gtk/gstreamer bindings could be released? Thanks, Nick On Fri, Feb 6, 2009 at 10:00 PM, Nick Hebner <[email protected]> wrote: > Anyone? Is this just impossible? What am I missing here? > > > On Wed, Feb 4, 2009 at 7:09 PM, Nick Hebner <[email protected]> wrote: > >> Is there any documentation on setting up a development version of elisa >> and pigment on Windows floating around anywhere? I have managed to get >> pigment built using OABuild, but I cannot really figure out what to do next. >> How to I install the gstreamer/glib/etc dlls into elisa or let elisa know >> where to find them? >> >> Thanks, >> >> Nick >> > >
