Re: Re: 2.2.4 release soon?

On Tue, 2003-07-22 at 18:38, Sam Varshavchik wrote:
> Kristian G. Kvilekval writes:
> 
> > Yes.. I've been waiting for some time lately to 
> > push out a bug fix release.   
> > 
> > Tell you what..  here's a pre-release file using
> > the new build system.   Can you try it out and let
> > me know your success or any troubles you have?  
> > Include output of configure and make.. Thx.
> > 
> > http://www.cs.ucsb.edu/~kris/zinf-2.2.4.tar.gz
> 
> A few Linux notes:
> 
> 1)
> 
> The configure script, manages to find Freetype version 1 include files, and 
> tries to build the freetype plugin, and fails.  I think that's because the 
> code actually needs Freetype 2; however it is not an issue on Linux since 
> Truetype support is built into xfs these days, so freetype can be disabled.

We actually depends on freetype-1.  You've mentioned (and sent a patch)
that would make linking with freetype irrelevant.  However,  my version
of zinf linked with freetype-1 looks much better than the one without.  
Not sure why as I am using X 4.2 with freetype pluglin loaded.? 
Probably
the code chooses a simpler font when 
not using freetype.  In fact, the font
option pane seems to do nothing  when
there is no freetype.


> 2)
> 
> The Corba plugin doesn't build.  In ui/corba/Makefile.am:
> 
> BUILT_SOURCES = Zinf.h
> 
> This needs to be replaced with:
> 
> BUILT_SOURCES = Zinf-common.c
> 
> Zinf.h is nowhere to be found, it is autogenerated by the Zinf-common 
> target.

I've never tried it.. 


> 3_
> 
> In the top level Makefile.am, three occurences of 
> $(pkglibdir), in the install-ln-plugins and uinstall-hook targets, need to 
> use $DESTDIR:
> 
> install-ln-plugins:
>         for plugin in $(DESTDIR)$(pkglibdir)/plugins/*.la ; do \
>            dir=`dirname $$plugin`; \
>            name=`basename $$plugin .la`; \
>            lib="$$dir/$$name$(so_ext)"; \
>            if [ -e "$$lib" ]; then \
>              mv $$lib $$dir/`echo $$name | sed 's/-/./'`; \
>            fi \
>         done
>         rm -f $(DESTDIR)$(pkglibdir)/plugins/*.la
>  
> uninstall-hook:
>         rm -f $(DESTDIR)$(pkglibdir)/plugins/*.{ui,pmi,pmo,lmc,mdf,ftf,plf,ppp}
> 4)
> 
> The first time I run zinf, it aborts with an error:
> 
> No UI plugin in '.:~/.zinf:/usr/lib/zinf' matched 'plugins/zinf.ui' or 'plugins/zinf.ui.ui.'
> Zinf will quit.

This has been happening for a while.. anybody feel like tracking it
down?

> The second and subsequent times it starts up, but with a couple of errors:
> /usr/lib/zinf/plugins/cd.lmc: undefined symbol: _ZN12PipelineUnit5PauseEv
> /usr/lib/zinf/plugins/wav.lmc: undefined symbol: _ZN12PipelineUnit5PauseEv
> 
> The problem is the PipelineUnit class.  It's part of libio, and libio is in 
> zinf_LDADD, however nothing in zinf mainline code refers to this class, so 
> this class never gets linked into the main executable.  It's referenced from 
> these two plugins, but because the class never got linked into the main 
> executable, the plugins fail to load.
> 
> Here's an ugly hack that'll force a reference, and get the class included in 
> the main executable.  A proper fix would be to change the makefiles 
> somehow...
> 
> After I fixed that, with the following hack, I discovered that the 
> EventBuffer class similarly needs to be manually hacked in:
> 
> --- base/src/player.cpp.orig	2003-07-22 17:15:38.000000000 -0400
> +++ base/src/player.cpp	2003-07-22 21:21:48.000000000 -0400
> @@ -2264,3 +2264,13 @@
>  
>      delete pmo;
>  }
> +
> +#include "pipeline.h"
> +#include "eventbuffer.h"
> +
> +static void hack()
> +{
> +	PipelineUnit hack1(NULL);
> +	EventBuffer hack2(0, 0, NULL);
> +}
> +

Eek. Andreas is there a better for this?


> 5)
> 
> Finally: the RIO PMP 300 plugin doesn't build.  I looked at the code 
> briefly, and the fixes seems to be trivial.  I don't have a RIO so I can't 
> test this, but the attached patch gets the plugin to compile for me.

I'll put it in and hope somebody tests it.  


-- 
Kristian G. Kvilekval
email:[email protected] office:(805)893-4276 http://www.cs.ucsb.edu/~kris



-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0