Colin Watson wrote:
On Thu, Jun 28, 2007 at 11:13:10AM +0200, Attilio Fiandrotti wrote:With gtk+ 2.10.13 from debian archives, the GDK_WINDOWING_DIRECTFB is still not defined (while it is when building gtk/dfb from sources), hence we cannot depend on it to enable at compile time the code (whatever it is) that performs keymap reloading.So i wonder if we can set a proper define when --enable-d-i configuration switch is used (which, i guess, is turned on when building for the d-i),It is, yes.and depend on it to compile in keymap reloading and possibily other d-i specific options in the GTK frontend.Any opinion on this?I think that's reasonable.
Basing on answers from Colin and Loic, I've applied a patch (r47807) which compiles in DirectFB specific code only if DI_UDEB was set at compile time. This is a first step in having cdebconf building against gtk/x11 too, but is not enough, so i'm leaving this bug open. Infact, in the GTK frontend's Makefile we always take compiler and linker flags from gtk+-directfb-2.0 package, and this always results in a gtk/dfb build of the frontend. So, we lack a clean way to get a gtk/x11 build of cdebconf's GTK frontend, which is required if someday cdebconf is going to replace debconf.
I think the frontend should be built against gtk/x11 by default, unless the --enable-di flag is set: to achieve this, the proper pkg-config's package should be called basing on the flag. This would allow easy locale cdebconf building, testing and deployment in an x11 environment.
I'd like to hear oter people's opinion on this idea. regards Attilio