Message: previous - next
Month: April 2012

Re: [trinity-devel] amarok on Arch - Success & Failure (yauap, mtp, riokarma, daap)

From: "David C. Rankin" <drankinatty@...>
Date: Sun, 01 Apr 2012 00:49:59 -0500
On 03/31/2012 10:12 PM, Darrell Anderson wrote:
> I just built Amarok with the following build options:
> -DWITH_YAUAP=ON \   <---
> -DWITH_MTP=ON \     <---
> -DBUILD_ALL=ON || exit 1
> DAAP was covered in a previous post about ruby. The MPV42 problem is covered by bug report 346. I don't have the support package installed for IFP. I am not going to try with RIOKARMA because the libkarma libs require the mono overhead.

My curiosity was mainly in building the full package to make sure it built and
confirming the code. I concur with riokarma and mono, but dead code hanging off
any branch of the GIT tree serves no one. I'll update the bug reports tomorrow.
I have to fix my yauap build script on my box before testing that part of the
code further. It was actually a great exercise to step though the different
build issues and either fix them or run them to the point where I exhausted my
knowledge and allowable time.

Thanks for the follow-up and adding to the pool of knowledge I'm drinking from :)

David C. Rankin, J.D.,P.E.