Debugging error to ensure necessitas on MacOS X Lion runs properly

[Nalin Savara]

Hi All, Ray,

Firstly Ray thank you a lot for your detailed and encouraging reply-- much
appreciated-- and I am honoured to share your knowledge and wisdom.

Secondly, my comments below:

On Wed, Jul 4, 2012 at 4:23 AM, Ray Donnelly <mingw.android at gmail.com>wrote:

> Hi Nalin,
>
> > 1. Faced the error described below ? Drop me a unicast mail OR mail
> on-list.
>
> I replied off-list last time you mentioned your problem with
> Necessitas on Mac, and I tracked your problem down to the fact that
> you were compiling for armv7a and trying to run that on android-7.
>
> The android emulator only supports armeabi with platform <= 13. To quote
> myself:
>
> "DId you try armeabi (or platform >= 14) yet?"
>
> You never got back to me on that question ;-)
>
> So please try that. For best results though I'd recommend using a
> device instead of the emulator.
>
> Thank you-- I will try that and report on-list shortly regarding that.
 Will also try to collect my experiences/thoughts in a wiki/blog/faq at
some time-- so that the learnings and Ray's advice can be shared and built
upon.

> I want to ultimately add to necessitas creator on ios enough that we can
> cross-compile apps for ios devices-- ipad/iphone/ipods.
>
> Well, I'm not sure how relevant Necessitas is for iOS to be honest,
> many of us are fans of Free and Open Source Software and iOS is
> ideologically firmly in the proprietary camp. From a purely "wow,
> that's cool" perspective, I'd love to be able to develop iOS apps on
> Qt Creator, but from every other perspective... here's my take:
> <snip>
>

My thinking is:-

(1) to use a .pro file + working Qt program--->> and use scripts etc within
necessitas to call apple tools and generate the required iOS deployment
bundle-- and either deploy them using Apple's commandline toolchains etc...
or to use XCode to deploy it to ios device.
Being able to use a .pro file to generate ios deployment bundle-- without
modifying-- will be a huge achievement-- and will save massive effort; and
especially on iPad it will be heaven-- to run on both iPad and Galaxy tabs
etc.

(2) Regarding static linking libraries-- sure... we can add terms that for
free/Open Source SW only it is legal.
For commercial software-- dev obviously has to buy Qt license-- since
apple's terms dont allow LGPL-ed libraries to be dynamically loaded.

(3) Debugging: Either we use XCode to debug OR we use gdb shipped with
xcode/ios toolchain-- with it's output piped to Qt-Creator window.
Probably we'll have to use XCode only.
It will be probably too much effort keeping debug code in sync with apple's
latest changes.

Regarding jailbreaking:: personally I'm not in favour of that.

All I want is that:-
(a) Qt programs that run on android, linux, windows-- can be deployed as
proof-of-concept on ios.
(b) Lot of sales of Qt licenses for ios dev will probably help Qt's
ecosystem also.
(though ofcourse... probably you guys will think of my save-the-world and
my love for "old Nokia" to be craziness.

What say ?

Regards,

Nalin
ps: Ray-- thanks again for reply-- really your knowledge is awesome and
contributions commendable-- and I have printed the mail-- to look at for
inspiration somedays when I am feeling down.

pps: pardon my somewhat short reply-- but this is all I wanted to say...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/necessitas-devel/attachments/20120705/d71f100e/attachment.html>