[SailfishDevel] Help for Syncthing App

[Oleksii Serdiuk]

Here's how I package libQt5SystemInfo library in TAO Translator 
(https://olse.me/taot):

1. Put an arch-specific binary into rpm/lib/<arch> folder.

https://olse.me/w0h


2. Add the following rule to .pro file:

 > libs.files = rpm/lib/$${QT_ARCH}/*
 > libs.path = /usr/share/$${TARGET}/lib

https://olse.me/ijM


3. Add the following packaging rules to .yaml and .spec:

.yaml:
 > ...
 > Files:
 > ...
 >   - '%{_datadir}/%{name}/lib'
 > ...

.spec:
 > ...
 > # >> macros
 > %define __requires_exclude ^libQt5SystemInfo.*$
 > %define __provides_exclude_from ^%{_datadir}/.*$
 > # << macros
 > ...

https://olse.me/2mJ


On 14/03/16 17:19, Michael Fuchs wrote:
> Good point.
> But I need it for packaging the proper syncthing binary.
>
>
> Am 14.03.2016 um 17:03 schrieb Pami Ketolainen:
>> On 03/14/2016 04:49 PM, Michael Fuchs wrote:
>>> Right, the colons where missing. But this was just an example, which I
>>> know from the documentation. I would need it to have two different
>>> values for tablet and phone. It's got to be sth like:
>>>
>>> arm: VAR = ARMVALUE
>>> x86_32: VAR = x86VALUE
>>>
>>
>> There probably is a way to detect the architecture during build time,
>> but in general that is not the right way to differentiate between
>> different types of devices. Because there could be ARM tablets and x86
>> phones.
>>
>> Most likely if you need to do some decisions based on the device type,
>> you should do that at run time.

-- 
With best regards,
Oleksii Serdiuk

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4372 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.sailfishos.org/pipermail/devel/attachments/20160316/733af4ff/attachment-0001.bin>