OK, it seems like most servers did not like my .bat attachment. I've put it, as well as the explanations on a wiki page: http://elisa.fluendo.com/wiki/TipsAndTricks/HackOnWindows
Guillaume Le vendredi 13 février 2009 à 19:44 +0100, Guillaume Emont a écrit : > Hi Nick, and thanks for your motivation to develop on Elisa. > > Sorry for the late reply, but we've been quite busy recently, working on > a cool feature to be included in the next release (should be next > Monday). > > Fortunately, to work on the development version of Elisa, you don't need > to compile anything. All you need is: > - The latest Elisa installed > - bzr (get it from http://www.bazaar-vcs.org) > - the attached set_env_installed.bat > > We're working on making this easier, but for now, there are some manual > steps involved so that you can change your installed elisa into > something that works for development. All these instructions assume > Elisa is installed in C:\Program Files\Elisa > > 1/ Copy the gstreamer and elisa-plugins-codecs .egg plugins from C: > \Program Files\Elisa\elisa-plugins into your %USERPROFILE%\.elisa-0.5 > \plugins (%USERPROFILE% is typically C:\Documents and Settings\<user > name> on XP and C:\Users\<user name> on Vista) > 2/ Double-click on the attached script (you would need to modify it if > elisa is installed in another directory than C:\Program Files\Elisa). > That will give you a command shell with everything set up to play with > elisa > 3/ Get elisa: bzr branch lp:elisa > 4/ cd elisa > 5/ Now you can launch your uninstalled elisa by typing: > python elisa-core\bin\elisa > 6/ Play with the code in your Elisa branch, add things, make > modifications, and share your code with the community! > > Outside of these steps, you probably want to remove all the other > plugins in your .elisa-0.5\plugins directory. > > Hope you will enjoy :) > > Guillaume > > Le vendredi 13 février 2009 à 08:31 -0800, Nick Hebner a écrit : > > Does anyone have any information on setting this up? Is the Windows > > build environment supported outside of Fluendo? If it is an internal > > only thing, then I can just move on and stop whining. > > > > Thanks, > > > > Nick > > > > On Sun, Feb 8, 2009 at 1:50 PM, Nick Hebner <[email protected]> wrote: > > 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 > > > > > > > > > >
