gnash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash] gnash testing


From: Rob Savoye
Subject: Re: [Gnash] gnash testing
Date: Thu, 13 Apr 2006 10:12:17 -0600
User-agent: Thunderbird 1.5 (X11/20051025)

Jens Petersen wrote:

Hmmm, pkgconfig doesn't seem an unreasonable dependency to me, considering that libxml2, gtk2, cairo, pango, glib2, and gtkglext all support it.

Right. But those are new dependencies for the GTK version of the player. pkgconfig isn't supported on all platforms though, for instance it would make cross-compiling with MingW or VC++ impossible, or other embedded platforms like eCOS or VxWorks. Gnash isn't just for the desktop...

I dunno, personally I would rather "configure" failed than "make". :) IMHO not using pkgconfig will lead to unnecessary configure maintenance work.

It's not unnecessary, it's the only way to get a truly portable configure and build system. I have no fear of writing pile of bourne shell code, nor debugging configure scripts. I agree configure should fail instead of make, but hey, Gnash is still a new project under heavy development...

Anyway the main problem with current configure file seems to be for the gtk family of libs. This is what configure gives on my FC5 x86_64 box:

The GTK tests are the newest ones added to Gnash, so it's not entirely unlikely they have subtle bugs like this. The difficulty of debugging configure scripts is only limited to the amount of different machines I have access to. I kindof hated adding so many dependencies to Gnash, but it turned out to be the only way to make the plugin work well in Firefox.

Configured paths for x86_64-redhat-linux-gnu are:
The simple pkgconfig hack patch I posted in my original mail at least makes it build on x86_64 for me on both FC4 and FC5 (and on i386 too of course).

All this has added is the path to the config files, which I've never needed to do to build Gnash on any platforms, They should probably be included though, so I'll add them to the macros. I don't mind a hack that'll use pkgconfig if present, and then drop into my own tests if not. I'll look into it when I add these additional include paths.

        - rob -




reply via email to

[Prev in Thread] Current Thread [Next in Thread]