Hi Dylan,
The qdoc tool is available in the build targets. Build QtFeedback from the
source branch of this pull request [1] and it will package docs as well.
BR,
Martin
[1] https://git.merproject.org/mer-core/qtfeedback/merge_requests/2
From: Devel [devel-boun.
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 ha
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 :
> Hi!
>
>
> Hello. I'm developing application with liboauth dependency. This library
>
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
Hi,
I just get notified by email by community member that my app (Jolla
Together) has been crashing and Jolla store has many reports on that for
many months already. Would be good that developer would get those store
comments to email.
But my question is if there is already a known fix/workaround
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
