trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: June 2014

Re: [trinity-users] libr-dev, gettext-kde

From: Michael Howard <mike@...>
Date: Sun, 01 Jun 2014 08:47:34 +0100
On 31/05/2014 21:09, Timothy Pearson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA224
>
>> On 31/05/2014 17:20, Slávek Banko wrote:
>>> On Saturday 31 of May 2014 17:42:58 Michael Howard wrote:
>>>> On 31/05/2014 16:30, Michele Calgaro wrote:
>>>>>>> As I'm currently facing the same problem, does anybody know the
>>>>>>> answer?
>>>>>>> Michele, did you get an answer?
>>>>>> The simplest option is to add the apt source with build dependencies.
>>>>>> You have three options for this:
>>>>>> 1) nightly-build-deps - but contain multiple packages that are not
>>>>>> needed: deb
>>>>>> http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-build
>>>>>> s/debian _distribution_ main 2) deps-r14 (on build-farm) - contain
>>>>>> only
>>>>>> the necessary packages: deb
>>>>>> http://ppa.quickbuild.pearsoncomputing.net/slavek-banko/deps-r14/ubuntu
>>>>>> _distribution_ main 3) deps-r14 (alternative) - same as 2), wider
>>>>>> bandwidth, contain packages also for mips deb
>>>>>> http://mirror.xcer.cz/trinity-sb _distribution_ deps-r14
>>>>> Hi Michael,
>>>>> Slavek already gave you good advice.
>>>>> Another way is to build libr and gettext-kde from sources, as I do.
>>>>> You
>>>>> can use this sources, from the same Slavek's repo. deb-src
>>>>> http://mirror.xcer.cz/trinity-sb jessie deps-r14 main-r14 Just replace
>>>>> jessie with the distro you are using.
>>>>> If you want, you can first browse it at
>>>>> http://mirror.xcer.cz/trinity-sb/dists/
>>>>>
>>>>> Just for your understanding, to build TDE in Debian and Ubuntu you
>>>>> need
>>>>> some extra packages which are not part of the main TDE repo. libr and
>>>>> gettext-kde are two of them. You  can find the others at the address
>>>>> indicated. Also when building, remember to bump up the version number
>>>>> of
>>>>> all packages (**EXCEPT** the deps-r14 ones) to 4:14.0.0 to avoid
>>>>> broken
>>>>> dependecies).
>>>> Sorry, forgot to clarify. Do you mean that _all_ packages, e.g. Amarok,
>>>> should be versioned at 4:14.0.0 ?
>>>>
>>>> Cheers,
>>>> Mike.
>>> If I understand correctly, you want to build amarok package only, not
>>> the
>>> complete set of TDE packages. In this case, you just deal with a version
>>> of
>>> the amarok package.
>>>
>> Actually, I'm building the complete set. For both amd64 and arm*.
>>
>> I have built, and use R14 from source from a year or more ago, using
>> source from GIT but not paying any attention to packaging. Both for
>> amd64 & armel.
>>
>> I am currently going through the process of building from GIT source
>> again, this time packaging. Firstly for amd64 and once complete, for
>> armv7hf (I have anumber of ARM devices/requirements).
>>
>> I use Amarok as an example as that is my media player of choice, and I
>> use it to play audio, from ARM devices, over the network.
>>
>> Amarok armv7hf from nightly builds does not work and I've noticed that
>> from building (amd64) using tde_packaging (from git) that the debian
>> build does not appear to use cmake but instead uses autotools?. Very
>> odd. Is that correct?
>>
>> Any info appreciated.
>>
>> Cheers,
>> Mike.
> How does Amarok fail on the armv7hf platform?
>
>
Hi Tim,

The amarokcollectionscanner does not work. However its run (all db 
backends) it results in no collection.

Running from command line gives no clues.

When I get cahnce I'll try rebuilding directly on an armv7 device.

If I can help debug the issue Id be happy to help.

Cheers,
Mike.

--