Found out the problem with building qt android platform plugins...

[BogDan]

Hi Ray,

I replaced "QTBUILDLIBS=$$find(target.path, "/files/qt/")
isEmpty( QTBUILDLIBS ): {" with isEmpty(QT_BUILD_TREE) which should be defined when you are building Qt.

I'm doing some test and I'll push my modifications.

Cheers,
BogDan.

P.S. I also added x86 support for android ;-)



----- Original Message -----
> From: mingw android <mingw.android at gmail.com>
> To: BogDan <bog_dan_ro at yahoo.com>; necessitas-devel at kde.org
> Cc: 
> Sent: Monday, July 18, 2011 11:08 AM
> Subject: Re: Found out the problem with building qt android platform plugins...
> 
> Hi BogDan,
> 
> The issue isn't whether they need android specific libraries, the
> thing is, when we're building Android Qt itself, we've got to get all
> of the plugins (android or not) to go down the path in qt.prf where we
> check if the path contains files/qt and if so don't modify it to
> /libs/armeabi*:
> 
>         QTBUILDLIBS=$$find(target.path, "/files/qt/")
>         isEmpty( QTBUILDLIBS ): {
>             CONFIG(armeabi-v7a) : target.path=/libs/armeabi-v7a/
>                            else : target.path=/libs/armeabi/
>         }
> 
> I think it's more proper to do QT += instead of QT = as that's what
> most of them do anyway and it seems useful to be able to know (e.g. in
> qt.prf) that they're being built for android.
> 
> However, so long as you can get all of the plugins to hit my
> QTBUILDLIBS check and not modify the path in that case, then it'll be
> fine.
> 
> Cheers,
> 
> Ray.
> 
> On Mon, Jul 18, 2011 at 8:31 AM, BogDan <bog_dan_ro at yahoo.com> wrote:
>>  Hi Ray,
>> 
>>  Hmm all (except platform plugin) Qt plugins don't need any android 
> specific libraries,
>>  so your change is not needed, I'll try to fix it today.
>> 
>>  BogDan.
>> 
>> 
>>  ----- Original Message -----
>>>  From: mingw android <mingw.android at gmail.com>
>>>  To: necessitas-devel at kde.org
>>>  Cc:
>>>  Sent: Sunday, July 17, 2011 2:01 AM
>>>  Subject: Found out the problem with building qt android platform 
> plugins...
>>> 
>>>  An update on this:
>>> 
>>>  I was being stupid about the armeabi/armeabi-v7a folder thing; we have
>>>  separate packages for different abis, but I think we could talk about
>>>  not doing this, instead having a leaf folder for each different abi?
>>> 
>>>  I've committed and pushed the fix for building android qt plugins
>>>  (qt.prf) with a commented out block which would achieve leaf folders
>>>  per abi (for the plugins anyway, of course there'd be a good few 
> other
>>>  issues), feel free to remove this commented out block altogether if
>>>  you think it's untidy to keep it there.
>>> 
>>>  When I was testing this, I noticed that some plugins weren't being
>>>  detected as android and so wouldn't hit that block, this was 
> because
>>>  those plugins overwrote QT = android with other stuff. I changed them
>>>  to use QT += instead. This shouldn't cause any problems. I'll 
> do more
>>>  testing on other platforms to make sure everything is ok.
>>> 
>>>  Cheers,
>>> 
>>>  Ray.
>>>  _______________________________________________
>>>  Necessitas-devel mailing list
>>>  Necessitas-devel at kde.org
>>>  https://mail.kde.org/mailman/listinfo/necessitas-devel
>>> 
>> 
>