HOWTO qt app without ministro

[Mario Fux]

Am Montag 19 November 2012, 20.18:23 schrieb Nalin Savara:

Morning Nalin

> While I agree 100% with BogDan and Ray...
> 
> A addendum (1) to the bit about "paying to bundle libs":-
> 
> > If there were a clean solution to this which costs me say $10000 I
> > would pay for it to override Ministro.
> 
> There are atleast 2 options for this:--
> 
> Option-1
> I believe if you buy commercial "Qt for Android"-- from Digia-- then you
> get the right to statically link to Qt libs... solve your problem... with
> added benefit of small size (see below)
> 
> This will give you two main benefits:--
> 
> 1. Statically linking means that you are essentially bundling parts Qt's
> libraries as part of your own executables.
> 
> 2. Assuming that "smart linking" is supported-- then, you will end up only
> linking classes/functions/pieces of code that are actually called... hence
> possibly using much less than the "40 MB to 100MB BogDan mentioned.
> 
> Buying Qt-commerical license will cost you much less than "$10,000"... and
> we must support Digia also... since they are serious about Android-Qt.
> 
> Option-2:
> Use one of the many "bundling libs" howtos-- by XumuK (in his list replies)
> ; by Izaar OR by me.
> Here's a link to a howto I posted on KDE's community wiki...
> http://community.kde.org/KDE_Community_Wiki:Community_portal

Great work, thx. But this is probably not the right place. More somewhere 
like:
http://techbase.kde.org/Projects/Necessitas

thx
Mario

> It includes sample code that bundles libs... but for Alpha-3 only... as
> want to put it on Github and figure out ethical implications of sharing
> first...
> 
> Regards,
> 
> Nalin
> 
> On Tue, Nov 20, 2012 at 12:29 AM, BogDan Vatra 
<taipanromania at gmail.com>wrote:
> > Hello,
> > 
> > Before I'll answer to some of your questions, I want to clarify a few
> > things.
> > We, the people behind Necessitas
> > (http://necessitas.kde.org/people.php), are doing this job for *FREE*
> > only on our spare time, just because we love to do it.
> > We are *COMMITTED* to do what *we believe* it is the best for Qt, for
> > developer and the most important for *USERS*.
> > 
> > Personally, I write a lot on this subject, but it sees it was not
> > enough, I'll do it one more time now.
> > You may wonder why I bother to create such a complicated flow and why
> > I didn't chose to bundled all the needed Qt libs together with the
> > application or to statically link the application with qt libs? The
> > answer is simple, if you bundle Qt libs your application package will
> > be *HUGE*, let me explain more: I had a hunch that there are a lot of
> > low-end devices (armv5) out there, so, I asked KDE sys-admins if I can
> > get simple statistics (download count) about the files which are
> > downloaded from kde.org, they kindly provide me the needed information
> > and my hunch become reality. According to these stats 45% are armv5
> > low-end devices, most of these devices have less than 512Mb of disk
> > space. If you plan to release an application that targets  two
> > platforms you'll need to bundle Qt libs twice (e.g. armv5 and armv7),
> > so your package will need 40-100Mb *ONLY* for Qt libs (if you plan to
> > add VFP support for armv5 and NEON for armv7, you'll need to double
> > that size). For the most Android users (not only for those how have
> > low-end devices) is not acceptable to download 100Mb fo
> 
> <snip>


-- 
Fellow of the FSFE.org and Joined the Game of KDE.org
Main Organizer of the Randa Meetings
And if you need a simple computer:
www.asimplecomputer.com or www.eineinfachercomputer.com