Jason Tackaberry wrote:
> On Sun, 2008-11-30 at 20:39 +0100, Dirk Meyer wrote:
>
>> That is odd, that is what kaa.base is doing to detect imlib2
>> support. Can you try to debug the library functions in
>> kaa.base.distribution.core?
>>
>
> Yeah, I'm not sure what's going on here, but if yo
On Sun, 2008-11-30 at 20:39 +0100, Dirk Meyer wrote:
> That is odd, that is what kaa.base is doing to detect imlib2
> support. Can you try to debug the library functions in
> kaa.base.distribution.core?
Yeah, I'm not sure what's going on here, but if you could add some
debugging to kaa/base/src/di
John Molohan wrote:
> None?
>
> [EMAIL PROTECTED] ~]# vim test.c
> [EMAIL PROTECTED] ~]# cc test.c `imlib2-config --libs --cflags`
> [EMAIL PROTECTED] ~]#
That is odd, that is what kaa.base is doing to detect imlib2
support. Can you try to debug the library functions in
kaa.base.distribution.core?
Jason Tackaberry wrote:
> On Fri, 2008-11-28 at 22:43 +, John Molohan wrote:
>
>> I'm a bit puzzled now but have probably missed something?
>>
>
> Is this a 64-bit platform?
>
Nope.
> Try compiling this short file, call it test.c:
>
> #include
>
> int main(i
On Fri, 2008-11-28 at 22:43 +, John Molohan wrote:
> I'm a bit puzzled now but have probably missed something?
Is this a 64-bit platform?
Try compiling this short file, call it test.c:
#include
int main(int argc, char **argv) {
imlib_context_set_display(
Jason Tackaberry wrote:
> On Mon, 2008-11-24 at 10:56 +0100, Dirk Meyer wrote:
>
>> kaa.display X11, Framebuffer and SDL all work with imlib2 or evas, if we
>> remove evas, imlib2 is a requirement. About the dfb support: it only
>> opens a surface. What is this good for? Ok, with evas you can us
Jason Tackaberry wrote:
> On Mon, 2008-11-24 at 23:02 +, John Molohan wrote:
>
>> So display still doesn't pick up imlib2 (from what you said it uses it
>> separately from kaa-imlib2 so I can stop worrying about compiling
>> that?). Any pointers on where I'm going wrong?
>>
>
> Ah, it
On Mon, 2008-11-24 at 23:02 +, John Molohan wrote:
> So display still doesn't pick up imlib2 (from what you said it uses it
> separately from kaa-imlib2 so I can stop worrying about compiling
> that?). Any pointers on where I'm going wrong?
Ah, it sounds like your Imlib2 wasn't built with X1
Jason Tackaberry wrote:
> On Sun, 2008-11-23 at 23:22 +, John Molohan wrote:
>
>> SystemError: kaa-display compiled without imlib2 display support.
>>
> [...]
>
>> So kaa-display does seem that it was compiled without X11 imlib2 support
>> but I do have kaa-imlib2 installed:
>>
On Mon, 2008-11-24 at 10:56 +0100, Dirk Meyer wrote:
> kaa.display X11, Framebuffer and SDL all work with imlib2 or evas, if we
> remove evas, imlib2 is a requirement. About the dfb support: it only
> opens a surface. What is this good for? Ok, with evas you can use evas
> on dfb, but if we drop ev
John Molohan wrote:
> + X11 (evas, evasGL, no imlib2)
> + Framebuffer (imlib2, evas)
> - DirectFB
> - SDL
That reminds me of something that we should do before we release
kaa.display: make imlib2 a requirement. And while we are changing stuff
like this: maybe remove the evas support. kaa.evas is
Jason Tackaberry wrote:
> On Sun, 2008-11-23 at 23:22 +, John Molohan wrote:
>
>> SystemError: kaa-display compiled without imlib2 display support.
>>
> [...]
>
>> So kaa-display does seem that it was compiled without X11 imlib2 support
>> but I do have kaa-imlib2 installed:
>>
On Sun, 2008-11-23 at 23:22 +, John Molohan wrote:
> SystemError: kaa-display compiled without imlib2 display support.
[...]
> So kaa-display does seem that it was compiled without X11 imlib2 support
> but I do have kaa-imlib2 installed:
kaa.display uses Imlib2 directly as well. It looks lik
Hi,
Having been catching up on the lists and trackers I saw Adam's skinnable
dialogues patch and was interested to try it out. It looks very
promising and it's already a big improvement on what was there. I've run
into an issue though. When playing a video with mplayer or xine I can no
longer
14 matches
Mail list logo
