FYI: sqlite is going to be allowed in the future versions - the PR was
accepted and this library should be available for linking in future. Thank
you all who made it happen!
Rinigus
On Mon, Mar 6, 2017 at 1:18 PM, rinigus wrote:
> Hi Martin
>
> Did you consider this
Hi Martin
Did you consider this recommendation?
>
> "To simplify matters, SQLite is also available as a pre-packaged
> amalgamation source code file: sqlite3.c. The amalgamation is a single file
> of ANSI-C code that implements the entire SQLite library. The amalgamation
> is much easier to deal
On 06/03/17 10:49, Martin Kampas wrote:
Hi Rinigus,
Did you consider this recommendation?
"To simplify matters, SQLite is also available as a pre-packaged
amalgamation source code file: sqlite3.c. The amalgamation is a single
file of ANSI-C code that implements the entire SQLite library. The
rg/howtocompile.html#amalgamation_versus_individual_source_files
From: Devel [devel-boun...@lists.sailfishos.org] on behalf of rinigus
[rinigus@gmail.com]
Sent: Saturday, March 04, 2017 2:46 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] SQLite linking
Hi,
Hi,
thank you very much for the response and explanation. Looking forward to
see the new whitelist / harbour rules. Its fine to take time to do it
properly, thanks for the feedback.
Best wishes,
Rinigus
On Sat, Mar 4, 2017 at 3:15 PM, Andrew Branson
wrote:
> Hi,
>
>
Hi,
I've had a look internally about this, and it's caught up in a larger overhaul
of the whitelist and harbour rules aiming to make development more attractive
to developers while remaining maintainable. This is part of the reason you
haven't had any feedback yet, but also everyone's got
Re OpenRepos: Sure, and I do. And through bundling I am publishing
@Harbour. But the main issue is the lack of response for a rather simple
request. Even a negative response is a response.
Sorry for complains. Enjoy the weekend and let's see if Jolla devs would
respond during the work hours :)
You can always use OpenRepos...
On March 4, 2017 8:50:37 AM GMT+01:00, rinigus wrote:
>Hi,
>
>one month + 10 days later - no response for PR nor SQLite linking from
>Harbour / Jolla devs. Already had to ship few versions with SQLite
>bundled
>with application as well. I'd
Hi Damien,
agreed, the topic of adding allowed libraries seems to be a sensitive one.
Which, in many cases, leads to inhibited development and wasting of time.
While I understand the limitations imposed on rather infrequently used
libraries due to inability to ensure Q, sqlite is probably used at
Hello,
Le samedi 04 mars 2017, rinigus a écrit :
> one month + 10 days later - no response for PR nor SQLite linking from
> Harbour / Jolla devs.
Well, the topic of adding allowed libraries seems to be a sensitive
one, without easy answering. You may propose this discussion for a
coming
Hi,
one month + 10 days later - no response for PR nor SQLite linking from
Harbour / Jolla devs. Already had to ship few versions with SQLite bundled
with application as well. I'd say its rather poor response times already
now (with the response time not reached yet).
Rinigus
On Wed, Jan 18,
Slava,
thank you for this constructive suggestion. I submitted PR
https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/pull/86 to add
sqlite into the list of allowed libraries. Hopefully, it will be accepted.
Best wishes,
Rinigus
On Wed, Jan 18, 2017 at 3:29 PM, Slava Monich
I believe rpm automatically detects the dependencies, even if they are
not in the spec. Removing the dependency from the spec might not help.
There may be some hackish ways of removing a dependency from the rpm
headers but I don't think that it would be a good idea. Better to spend
time on
>
>
> Is the automatic checker not allowing it through with sqlite3 as a
> requirement? Are you sure that you used the packagename used on jolla
> systems for the requirement?
>
During deployment as RPM, the specific error is
Requires
ERROR [libsqlite3.so.0] Cannot require shared
Though I have not done this myself yet 2 observations based on your mail:
1. Removing it from the dependency spec is bad (unless you statically link
see point 2), though it is currently widely used by system applications and
3rd party applications alike you can never know if in the future someone
Hi!
I wonder what is the best practice concerning linking to sqlite3?
It's probably always installed on devices/emulators and there is no problem
with deployment of an app requiring it. However, its a bit odd to just
cancel off the requirement in RPM SPEC, as I am supposed to do to get it
16 matches
Mail list logo