[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Problem building kdebase/workspace/kcontrol/kxkb
From:       "Andriy Rysin" <arysin () gmail ! com>
Date:       2007-10-20 18:11:06
Message-ID: 3e02eb610710201111j55419d5fpdfeb429d0466e041 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


2007/10/20, Brad Hards <bradh@frogmouth.net>:
>
> On Saturday 20 October 2007 08:55:04 pm Ilya Konstantinov wrote:
> > > would be better to try to selectively #ifdef out part of the
> > > functionality, or whether there is some alternative header,
> > > or whether we shouldn't try to compile this module.
> >
> > On my Debian system, /usr/include/X11/extensions/XKBfile.h resides in
> the
> > libxkbfile-dev. package Instead of selectively #ifdef-ing code, you
> should
> > instead try to locate which package in your distro provides it.
> My (fedora) system has a slightly different name.
>
> That isn't the point though. Shouldn't the configure checks verify whether
> the
> right dependencies are available, and do something to avoid breaking at
> compile time (e.g. alternative code path, or at least some notification)?


Yes, I will add a check for XKBfile and will disable kxkb altogether if
neither libxklavier nor XKBfile is present. Though there's a chance that (in
near future) if you don't have libxklavier it won't build kxkb at all as
code relying on xkbfile is quite old and is not really maintained properly.

Thanks for the report,
Andriy

[Attachment #5 (text/html)]

2007/10/20, Brad Hards &lt;<a \
href="mailto:bradh@frogmouth.net">bradh@frogmouth.net</a>&gt;:<div><span \
class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Saturday \
20 October 2007 08:55:04 pm Ilya Konstantinov wrote:<br>&gt; &gt; would be better to \
try to selectively #ifdef out part of the<br>&gt; &gt; functionality, or whether \
there is some alternative header,<br>&gt; &gt; or whether we shouldn&#39;t try to \
compile this module. <br>&gt;<br>&gt; On my Debian system, \
/usr/include/X11/extensions/XKBfile.h resides in the<br>&gt; libxkbfile-dev. package \
Instead of selectively #ifdef-ing code, you should<br>&gt; instead try to locate \
which package in your distro provides it. <br>My (fedora) system has a slightly \
different name.<br><br>That isn&#39;t the point though. Shouldn&#39;t the configure \
checks verify whether the<br>right dependencies are available, and do something to \
avoid breaking at <br>compile time (e.g. alternative code path, or at least some \
notification)?</blockquote><div><br>Yes, I will add a check for XKBfile and will \
disable kxkb altogether if neither libxklavier nor XKBfile is present. Though \
there&#39;s a chance that (in near future) if you don&#39;t have libxklavier it \
won&#39;t build kxkb at all as code relying on xkbfile is quite old and is not really \
maintained properly. <br><br>Thanks for the report,<br>Andriy<br></div><br></div>



>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]