[SailfishDevel] Packaging application with library
Oleg Linkin
maledictusdemagog at gmail.com
Thu Mar 29 19:02:11 UTC 2018
With number 1 I mean first link - no.2. I don't want to write my own qmake
file for liboauth and build it with project. What is the easiest way to
package non-qt lib with harbour app?
And I have created issue about adding liboauth to approved libs in validator
repository, but I am not sure that it helps
В письме от четверг, 29 марта 2018 г. 20:13:12 +03 пользователь Slava Monich
написал:
> Binaries is no. 2, see the harbour faq. The first variant may look like
> this:
>
> https://github.com/monich/harbour-books/tree/master/fribidi
> https://github.com/monich/harbour-books/tree/master/linebreak
>
> Basically, somehow pull the sources into your git, add them to your
> project and setup include paths and other compiler options so that the
> whole thing compiles.
>
> And of course there are many ways to do it. What I referenced is just an
> example and probably not the best one. But I hope it helps.
>
> Cheers,
> -Slava
>
> > I want to use variant 1, but don't understand how. Should I only
> > download *.so file from engine and package it with my application? Or
> > I need something more to do this?
> >
> > 2018-03-29 18:21 GMT+03:00 Slava Monich <slava.monich at jolla.com
> >
> > <mailto:slava.monich at jolla.com>>:
> > Hi!
> >
> > Hello. I'm developing application with liboauth dependency.
> > This library
> > exists in repos and I have installed it in SDK for building
> > and running app in
> > emulator. On phone this library exists too.
> > But this library is prohibited for harbour.
> > What the proper way to package my application for harbour?
> >
> > You have 4 options here:
> >
> > 1. Compile the library statically into your app
> > 2. Package the library with your app as described in the faq [1]
> > 3. Convince Jolla to add liboauth to the list of allowed libraries [2]
> > 4. Load pre-installed library with dlopen, e.g. [3]
> >
> > The last solution is a bit of a hack but it's probably acceptable
> > because liboauth doesn't seem to have had any known ABI breakages
> > in the past [4]. Which of course doesn't guarantee anything in the
> > future. Note that your rpm would have to depend on liboauth
> > package to make sure that the library gets installed together with
> > the app. Not sure if that would pass the store QA though.
> >
> > Cheers,
> > -Slava
> >
> > [1] https://harbour.jolla.com/faq#Shared_Libraries
> > <https://harbour.jolla.com/faq#Shared_Libraries>
> > [2]
> > https://github.com/sailfishos/sdk-harbour-rpmvalidator/blob/harbour-qa
> > /allowed_libraries.conf
> > <https://github.com/sailfishos/sdk-harbour-rpmvalidator/blob/harbour-> > qa/allowed_libraries.conf> [3]
> > https://github.com/monich/harbour-books/blob/master/app/stubs/libmagic
> > .c
> > <https://github.com/monich/harbour-books/blob/master/app/stubs/libmagi
> > c.c>
> > [4] http://upstream.rosalinux.ru/versions/liboauth.html
> > <http://upstream.rosalinux.ru/versions/liboauth.html>
More information about the Devel
mailing list