Bug#675138: weston: not installable, fails to build from source
On 12/06/13 10:58, Schrober wrote:
> On Wednesday 12 June 2013 10:44:10 Cyril Brulebois wrote:
>> Schrober <franzschrober@yahoo.de> (12/06/2013):
>>>> thanks for the heads-up on IRC by the way. Since binNMUs dramatically
>>>> failed due to yet another libpng mess, I'm pondering just uploading
>>>> weston to unstable instead, but I'd have to see which toy apps to enable
>>>> and how. That might take some days as it's low priority on my todo list.
>>>
>>> The weston situation in Debian is extreme frustrating. […]
>>
>> JFTR, a bunch of iterations were needed to get all of libdrm, wayland,
>> and mesa to build in experimental. weston will come after those.
>
> Just before a misunderstanding happens here: I didn't criticise the people
> behind all the stuff. I am extreme happy that there are some encouraged people
> which try to get this stuff working.
>
> It is just the situation that currently each step taken by me ended with my
> toe stubbed on another edge. It all started with me trying to fix some
> programs which don't work as expected under wayland and I still aren't at the
> point were I could reproduce the problem because I failed miserably to get the
> test environment to work at all.
I had weston and all the stack (libdrm, mesa, wayland, cairo, pixman, gtk+,
clutter...) built from git and working fairly well (I have a script in case
you're interested). Now that things in Debian are up to date except for weston,
you can probably build just weston though. libunwind is missing the .pcs in the
Debian packages indeed (I reported that bug) but you can --disable-unwind in
weston (I think a patch to autodetect if libunwind is present has been just
committed to git). As for cairo, it was disabled temporarily because of
multi-arch. I'll look at enabling it back again later today.
As for weston in Debian, I'm too busy lately but I want to get it updated. But
let's get cairo fixed first, then we can take care of weston.
Cheers,
Emilio
Reply to: