Re: [Interest] qt.git: broken v5.6.0 .gitmodules?

2017-12-09 Thread Christian Gagneraud 
On 10 December 2017 at 20:01, Thiago Macieira  wrote:
> On sábado, 9 de dezembro de 2017 22:00:24 PST Christian Gagneraud wrote:
>> > Correct, the branches don't exist anymore. The commits still do.
>>
>> Is it me or this is a serious issue?
>
> It's just you. The commits still exist and that's all that counts.
>
>> I need linux-32 custom build of Qt-5.6.x (and Qt-5.9.x), first Qt-5.6
>> dropped support for linux-32, and now the Qt Company/Project broke
>> branch/tag git build!
>
> Linux 32-bit builds are still supported, even in Qt 5.10. We don't create
> binaries for them because of the small percentage of people who need them, but
> they are supported.
>
> The build is not broken and nor is the tag.

Something is broken for sure.

From http://wiki.qt.io/Building_Qt_5_from_Git:
--
In order to build a specific release of Qt, you can checkout the desired tag:

$ cd qt5
$ git checkout v5.8.0
$ perl init-repository
--

This doesn't work anymore.

Chris
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] qt.git: broken v5.6.0 .gitmodules?

2017-12-09 Thread Thiago Macieira 
On sábado, 9 de dezembro de 2017 22:00:24 PST Christian Gagneraud wrote:
> > Correct, the branches don't exist anymore. The commits still do.
> 
> Is it me or this is a serious issue?

It's just you. The commits still exist and that's all that counts.

> I need linux-32 custom build of Qt-5.6.x (and Qt-5.9.x), first Qt-5.6
> dropped support for linux-32, and now the Qt Company/Project broke
> branch/tag git build!

Linux 32-bit builds are still supported, even in Qt 5.10. We don't create 
binaries for them because of the small percentage of people who need them, but 
they are supported.

The build is not broken and nor is the tag.

> I think there's a issue with other submodules that point to 'master'
> instead of '5.6.0':
>  - qtrepotools
>  - qtqa
>  - qtfeedback
>  - qtdocgallery

Those have never been part of any Qt release. That's why they are still 
"master".

> > I tried to change the branch to "." (which means "same as the
> > supermodule")
> > but that broke some scripts that I don't use and don't have any interest
> > in
> > fixing, so we keep changing the branch names.
> > 
> > If anyone is interested in fixing init-repository, I'd be very thankful.
> 
> Sorry, I gave up Perl, ages ago.

I still use Perl, all the time. I don't use init-repository.

Try using git submodule init && git submodule update instead.
-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] qt.git: broken v5.6.0 .gitmodules?

2017-12-09 Thread Christian Gagneraud 
On 10 December 2017 at 18:13, Thiago Macieira  wrote:
> On sábado, 9 de dezembro de 2017 19:30:41 PST Christian Gagneraud wrote:
>> Hi there,
>>
>> Is it me or .gitmodules on tag v5.6.0 is broken?
>> .gitmodules set the branch name of all qt modules to '5.6.0', but
>> these branches don't exist (anymore?). The only branches available on
>> qt submodules are '5.6, '5.7', ... and tags like 'v5.6.0', 'v5.6.1',
>
> Correct, the branches don't exist anymore. The commits still do.

Is it me or this is a serious issue?

I need linux-32 custom build of Qt-5.6.x (and Qt-5.9.x), first Qt-5.6
dropped support for linux-32, and now the Qt Company/Project broke
branch/tag git build!

I think there's a issue with other submodules that point to 'master'
instead of '5.6.0':
 - qtrepotools
 - qtqa
 - qtfeedback
 - qtdocgallery


> I tried to change the branch to "." (which means "same as the supermodule")
> but that broke some scripts that I don't use and don't have any interest in
> fixing, so we keep changing the branch names.
>
> If anyone is interested in fixing init-repository, I'd be very thankful.

Sorry, I gave up Perl, ages ago.

Chris

>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] qt.git: broken v5.6.0 .gitmodules?

2017-12-09 Thread Thiago Macieira 
On sábado, 9 de dezembro de 2017 19:30:41 PST Christian Gagneraud wrote:
> Hi there,
> 
> Is it me or .gitmodules on tag v5.6.0 is broken?
> .gitmodules set the branch name of all qt modules to '5.6.0', but
> these branches don't exist (anymore?). The only branches available on
> qt submodules are '5.6, '5.7', ... and tags like 'v5.6.0', 'v5.6.1',

Correct, the branches don't exist anymore. The commits still do.

I tried to change the branch to "." (which means "same as the supermodule") 
but that broke some scripts that I don't use and don't have any interest in 
fixing, so we keep changing the branch names.

If anyone is interested in fixing init-repository, I'd be very thankful.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Interest Digest, Vol 75, Issue 5

2017-12-09 Thread Thiago Macieira 
On sábado, 9 de dezembro de 2017 10:39:43 PST Nikos Chantziaras wrote:
> On 09/12/17 19:39, Thiago Macieira wrote:
> > On sábado, 9 de dezembro de 2017 07:51:11 PST Konstantin Tokarev wrote:
> >> That's a shame indeed. Redirecting people one by one to
> >> http://download.qt.io/official_releases/qt/ doesn't scale well.
> > 
> > It takes two clicks to go from https://qt.io to
> > https://www.qt.io/download-qt-for-application-development and the open
> > source version is right there.
> > 
> > That is, if you manage to click the "Start free Qt trial" button on the
> > homepage, since it moves the moment you hover the mouse over it.
> 
> I'm not sure why I would ever assume a "free trial" to take me to the
> Open Source or Free Software version of something :-/

I agree it's not obvious, but it's the most likely entry from the webpage 
since there's no Download button.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] qt.git: broken v5.6.0 .gitmodules?

2017-12-09 Thread Christian Gagneraud 
Hi there,

Is it me or .gitmodules on tag v5.6.0 is broken?
.gitmodules set the branch name of all qt modules to '5.6.0', but
these branches don't exist (anymore?). The only branches available on
qt submodules are '5.6, '5.7', ... and tags like 'v5.6.0', 'v5.6.1',
...

git clone $qt5url
cd qt5
git checkout $qt5version
perl init-repository ...
...
Cloning into 'qtandroidextras'...
fatal: Remote branch 5.6.0 not found in upstream origin
git clone --branch 5.6.0 https://code.qt.io/qt/qtandroidextras.git
qtandroidextras exited with status 32768 at init-repository line 191.
Qt::InitRepository::exe(Qt::InitRepository=HASH(0x9127ca0),
"git", "clone", "--branch", "5.6.0",
"https://code.qt.io/qt/qtandroidextras.git;, "qtandroidextras") called
at init-repository line 472

Qt::InitRepository::git_clone_one_submodule(Qt::InitRepository=HASH(0x9127ca0),
"qtandroidextras", "qt/qtandroidextras.git", "5.6.0") called at
init-repository line 378

Qt::InitRepository::git_clone_all_submodules(Qt::InitRepository=HASH(0x9127ca0),
"qt/qt5", 0, "preview", "essential", "addon", "deprecated",
"-qtactiveqt", ...) called at init-repository line 565
Qt::InitRepository::run(Qt::InitRepository=HASH(0x9127ca0))
called at init-repository line 576
+ '[' 2 -ne 0 ']'
+ echo 'ERROR: init-repository failed'
ERROR: init-repository failed
+ exit 1


The same problem appears with other qt5 submodules


Any clue how to fix this problem?


Chris
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Interest Digest, Vol 75, Issue 5

2017-12-09 Thread Thiago Macieira 
On sábado, 9 de dezembro de 2017 07:51:11 PST Konstantin Tokarev wrote:
> That's a shame indeed. Redirecting people one by one to
> http://download.qt.io/official_releases/qt/ doesn't scale well.

It takes two clicks to go from https://qt.io to 
https://www.qt.io/download-qt-for-application-development and the open source 
version is right there.

That is, if you manage to click the "Start free Qt trial" button on the 
homepage, since it moves the moment you hover the mouse over it.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Interest Digest, Vol 75, Issue 5

2017-12-09 Thread Konstantin Tokarev 


> On 12/09/2017 08:21 AM, Oliver Niebuhr wrote:
> 
>> I already contacted Digia directly and asked them this and other
>> Questions. Also gave those and more Details. But the only answer after a
>> few weeks was: "Thanks for contacting us. Please tell us what License
>> you want to buy" etc. They seem to hate the Open Source Community as
>> they never answer anything but instead you get contacted by a Sales
>> Person. So they are not helpful at all. At least from my experience.
> 
> Oliver,
> 
> That has been the experience of EVERY ONE of my clients. When
> they contact Digia to ask about what is and is not OpenSource
> sales calls back to tell them even "Hello World" needs a
> commercial license. So, rather than be a legitimate player in the
> OpenSource world, they attempt to be extortionists.
> 
> One thing I have found rather impressive. When your client has a
> very significant law firm ask the EXACT question, words and all,
> suddenly sales responds "Go with God my child. You have my
> blessing."

Sales are there to sale stuff. Not to provide you free consultations about
Open Source software, its licensing, etc. For these things you should
use different communication channels: mailing lists and IRC.

(Also, if someone has little experience with open source, but is not
limited in money, bying commercial license is indeed might be an
adequate solution)

> 
> Adding insult to injury, when a noob happens upon the Qt Web
> site, it is almost impossible for them to find and download the
> OpenSource version. Yes, people on here have saved the links and
> pass them around, but go there with the eyes of a noob and try to
> find the OpenSource version without filling out some form asking
> for as much personal information as Google gathers on everyone
> daily...

That's a shame indeed. Redirecting people one by one to
http://download.qt.io/official_releases/qt/ doesn't scale well.

> 
> Oh, Oliver. The answer to your question depends on the size and
> reputation of the lawyers you have asking it. You, me and everyone
> else will all have sales continue telling us even "Hello World"
> needs a commercial license.
> 
> --
> Roland Hughes, President
> Logikal Solutions
> (630)-205-1593
> 
> http://www.theminimumyouneedtoknow.com
> http://www.infiniteexposure.net
> http://www.johnsmith-book.com
> http://www.logikalblog.com
> http://www.interestingauthors.com/blog
> http://lesedi.us/
> http://onedollarcontentstore.com
-- 
Regards,
Konstantin
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Interest Digest, Vol 75, Issue 5

2017-12-09 Thread Roland Hughes 

On 12/09/2017 08:21 AM,  Oliver Niebuhr wrote:

I already contacted Digia directly and asked them this and other
Questions. Also gave those and more Details. But the only answer after a
few weeks was: "Thanks for contacting us. Please tell us what License
you want to buy" etc. They seem to hate the Open Source Community as
they never answer anything but instead you get contacted by a Sales
Person. So they are not helpful at all. At least from my experience.

Oliver,

That has been the experience of EVERY ONE of my clients. When they 
contact Digia to ask about what is and is not OpenSource sales calls 
back to tell them even "Hello World" needs a commercial license. So, 
rather than be a legitimate player in the OpenSource world, they attempt 
to be extortionists.


One thing I have found rather impressive. When your client has a very 
significant law firm ask the EXACT question, words and all, suddenly 
sales responds "Go with God my child. You have my blessing."


Adding insult to injury, when a noob happens upon the Qt Web site, it is 
almost impossible for them to find and download the OpenSource version. 
Yes, people on here have saved the links and pass them around, but go 
there with the eyes of a noob and try to find the OpenSource version 
without filling out some form asking for as much personal information as 
Google gathers on everyone daily...



Oh, Oliver. The answer to your question depends on the size and 
reputation of the lawyers you have asking it. You, me and everyone else 
will all have sales continue telling us even "Hello World" needs a 
commercial license.


--
Roland Hughes, President
Logikal Solutions
(630)-205-1593

http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.johnsmith-book.com
http://www.logikalblog.com
http://www.interestingauthors.com/blog
http://lesedi.us/
http://onedollarcontentstore.com

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Can't deploy anymore on QtCretor 4.5

2017-12-09 Thread Xavier Bigand 
I figured out how to fix the issue with playservices, but now I have a new
one :

Generating Android Package

Input file:
D:/Dev/Koalabs/HomeDesign3D/Projects/build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Debug/android-libHomeDesign3D.so-deployment-settings.json

Output directory:
D:/Dev/Koalabs/HomeDesign3D/Projects/build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Debug/android-build/

Application binary:
D:/Dev/Koalabs/HomeDesign3D/Projects/build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Debug/libHomeDesign3D.so

Android build platform: android-26

Install to device: No

The JavaCompile.setDependencyCacheDir() method has been deprecated and is
scheduled to be removed in Gradle 4.0.

The TaskInputs.source(Object) method has been deprecated and is scheduled
to be removed in Gradle 4.0. Please use
TaskInputs.file(Object).skipWhenEmpty() instead.

:preBuild UP-TO-DATE

:preDebugBuild UP-TO-DATE

:checkDebugManifest

:preReleaseBuild UP-TO-DATE

:prepareComAndroidSupportSupportCompat2520Library

:prepareComAndroidSupportSupportCoreUi2520Library

:prepareComAndroidSupportSupportCoreUtils2520Library

:prepareComAndroidSupportSupportFragment2520Library

:prepareComAndroidSupportSupportMediaCompat2520Library

:prepareComAndroidSupportSupportV42520Library

:prepareComGoogleAndroidGmsPlayServicesAds1104Library

:prepareComGoogleAndroidGmsPlayServicesAdsLite1104Library

:prepareComGoogleAndroidGmsPlayServicesBase1104Library

:prepareComGoogleAndroidGmsPlayServicesBasement1104Library

:prepareComGoogleAndroidGmsPlayServicesClearcut1104Library

:prepareComGoogleAndroidGmsPlayServicesGass1104Library

:prepareComGoogleAndroidGmsPlayServicesSafetynet1104Library

:prepareComGoogleAndroidGmsPlayServicesTasks1104Library

:prepareDebugDependencies

:compileDebugAidl

:compileDebugRenderscript UP-TO-DATE

:generateDebugBuildConfig UP-TO-DATE

:generateDebugResValues UP-TO-DATE

:generateDebugResources UP-TO-DATE

:mergeDebugResources

Error: Failed to crunch file
D:\Dev\Koalabs\HomeDesign3D\Projects\build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Debug\android-build\build\intermediates\exploded-aar\com.google.android.gms\play-services-base\11.0.4\res\drawable-hdpi-v4\common_google_signin_btn_icon_dark_normal_background.9.png
into
D:\Dev\Koalabs\HomeDesign3D\Projects\build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Debug\android-build\build\intermediates\res\merged\debug\drawable-hdpi-v4\common_google_signin_btn_icon_dark_normal_background.9.png

:mergeDebugResources FAILED


FAILURE: Build failed with an exception.


* What went wrong:

Execution failed for task ':mergeDebugResources'.

> Error: Failed to crunch file
D:\Dev\Koalabs\HomeDesign3D\Projects\build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Debug\android-build\build\intermediates\exploded-aar\com.google.android.gms\play-services-base\11.0.4\res\drawable-hdpi-v4\common_google_signin_btn_icon_dark_normal_background.9.png
into
D:\Dev\Koalabs\HomeDesign3D\Projects\build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Debug\android-build\build\intermediates\res\merged\debug\drawable-hdpi-v4\common_google_signin_btn_icon_dark_normal_background.9.png


* Try:

Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output.


BUILD FAILED







For play services I had the line:
compile 'com.google.android.gms:play-services-ads:11.0.4'

In the build.gradle files in the section dependencies, but I don't really
like to have a fixed version number that depend on my local configuration.



2017-12-09 11:42 GMT+01:00 Xavier Bigand :

> I got a lot more errors by doing that, so I put it back some of our
> configurations in the manifest while taking care of keeping changes of
> QtCreator, and I still have same errors.
>
> Sadly this workaround doesn't work for me.
>
>
>
> 2017-12-09 11:11 GMT+01:00 Nikos Chantziaras :
>
>> I ran into issues myself going from 4.4 to 4.5. But I didn't delve too
>> long into solving them manually. What I did instead is take a complete
>> backup of my project (this should go without saying, obviously,) and then
>> delete the Android files. Then I regenerated the Android files and
>> re-applied my custom settings in the template editor.
>>
>> This made sure gradle is used and everything built correctly.
>>
>> In other words, there doesn't seem to be an actual upgrade path
>> implemented in Creator. I might be wrong, but the best solution seems to be
>> to wipe the Android directory and re-generate it.
>>
>> The button that regenerates all the Android template files is a bit
>> hidden though:
>>
>> * Click on the "Projects" icon in the left pane (the wench icon.)
>>
>> * Select your Android Kit's "Build" entry.
>>
>> * In the "Build Steps" group, click the

Re: [Interest] Can't deploy anymore on QtCretor 4.5

2017-12-09 Thread Xavier Bigand 
I got a lot more errors by doing that, so I put it back some of our
configurations in the manifest while taking care of keeping changes of
QtCreator, and I still have same errors.

Sadly this workaround doesn't work for me.



2017-12-09 11:11 GMT+01:00 Nikos Chantziaras :

> I ran into issues myself going from 4.4 to 4.5. But I didn't delve too
> long into solving them manually. What I did instead is take a complete
> backup of my project (this should go without saying, obviously,) and then
> delete the Android files. Then I regenerated the Android files and
> re-applied my custom settings in the template editor.
>
> This made sure gradle is used and everything built correctly.
>
> In other words, there doesn't seem to be an actual upgrade path
> implemented in Creator. I might be wrong, but the best solution seems to be
> to wipe the Android directory and re-generate it.
>
> The button that regenerates all the Android template files is a bit hidden
> though:
>
> * Click on the "Projects" icon in the left pane (the wench icon.)
>
> * Select your Android Kit's "Build" entry.
>
> * In the "Build Steps" group, click the "Details" button of the "Build
> Android APK" entry. This will expand it.
>
> * There should now be a "Create Templates" button.
>
>
> On 09/12/17 11:55, Xavier Bigand wrote:
>
>> Yes, but QtCreator 4.4 had a bug when we get the SDK from Android Studio
>> instead of the stand alone version that is no more accessible.
>>
>> QtCreator 4.5 which support the SDK from Android Studio tells me that
>> everything is ok with my Android configuration, but now with gradle instead
>> of ant I can't deploy.
>> We didn't do any change on the manifest file, so I don't understand the
>> issue.
>>
>> 2017-12-09 8:47 GMT+01:00 Nikos Chantziaras  rea...@gmail.com>>:
>>
>>
>> You need to edit the Android manifest file, not the pro.user file.
>> Creator has a special editor dialog for it.
>>
>>
>>
>> On 09/12/17 02:05, Xavier Bigand wrote:
>>
>> Hello,
>>
>> It seems to be a nice version, but I still have some trouble
>> when targeting Android, with the version 4.4 I had to edit the
>> .pro.user to make the deployment working by forcing the
>> BuildTargetSdk at android-26. But now it seems that something
>> different goes wrong, here is my output:
>>
>> 00:39:06: Le processus
>> "D:\Softs\SDK\Qt\Tools\mingw530_32\bin\mingw32-make.exe" s'est
>> terminé normalement.
>> 00:39:06: Starting:
>> "D:\Softs\SDK\Qt\5.9.3\android_armv7\bin\androiddeployqt.exe"
>> --input
>> D:/Dev/Koalabs/HomeDesign3D/Projects/build-HomeDesign3D-Andr
>> oid_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Deb
>> ug/android-libHomeDesign3D.so-deployment-settings.json
>> --output
>> D:/Dev/Koalabs/HomeDesign3D/Projects/build-HomeDesign3D-Andr
>> oid_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Deb
>> ug/android-build
>> --deployment bundled --android-platform android-26 --jdk
>> "C:/Program Files/Java/jdk1.8.0_112" --gradle
>> Generating Android Package
>> Input file:
>> D:/Dev/Koalabs/HomeDesign3D/Projects/build-HomeDesign3D-Andr
>> oid_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Deb
>> ug/android-libHomeDesign3D.so-deployment-settings.json
>> Output directory:
>> D:/Dev/Koalabs/HomeDesign3D/Projects/build-HomeDesign3D-Andr
>> oid_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Deb
>> ug/android-build/
>> Application binary:
>> D:/Dev/Koalabs/HomeDesign3D/Projects/build-HomeDesign3D-Andr
>> oid_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Deb
>> ug/libHomeDesign3D.so
>> Android build platform: android-26
>> Install to device: No
>> The JavaCompile.setDependencyCacheDir() method has been
>> deprecated and is scheduled to be removed in Gradle 4.0.
>> The TaskInputs.source(Object) method has been deprecated and is
>> scheduled to be removed in Gradle 4.0. Please use
>> TaskInputs.file(Object).skipWhenEmpty() instead.
>> :preBuild UP-TO-DATE
>> :preDebugBuild UP-TO-DATE
>> :checkDebugManifest
>> :prepareDebugDependencies
>> :compileDebugAidl
>> :compileDebugRenderscript
>> :generateDebugBuildConfig
>> :generateDebugResValues
>> :generateDebugResources
>> :mergeDebugResources
>> :processDebugManifest
>> D:\Dev\Koalabs\HomeDesign3D\Projects\build-HomeDesign3D-Andr
>> oid_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Deb
>> ug\android-build\AndroidManifest.xml:78:5-66
>> Warning:
>> Element uses-permission#android.permission.INTERNET at
>> AndroidManifest.xml:78:5-66 duplicated with element declared at
>> AndroidManifest.xml:67:9-71
>>

Re: [Interest] Can't deploy anymore on QtCretor 4.5

2017-12-09 Thread Nikos Chantziaras 
I ran into issues myself going from 4.4 to 4.5. But I didn't delve too 
long into solving them manually. What I did instead is take a complete 
backup of my project (this should go without saying, obviously,) and 
then delete the Android files. Then I regenerated the Android files and 
re-applied my custom settings in the template editor.


This made sure gradle is used and everything built correctly.

In other words, there doesn't seem to be an actual upgrade path 
implemented in Creator. I might be wrong, but the best solution seems to 
be to wipe the Android directory and re-generate it.


The button that regenerates all the Android template files is a bit 
hidden though:


* Click on the "Projects" icon in the left pane (the wench icon.)

* Select your Android Kit's "Build" entry.

* In the "Build Steps" group, click the "Details" button of the "Build 
Android APK" entry. This will expand it.


* There should now be a "Create Templates" button.


On 09/12/17 11:55, Xavier Bigand wrote:
Yes, but QtCreator 4.4 had a bug when we get the SDK from Android Studio 
instead of the stand alone version that is no more accessible.


QtCreator 4.5 which support the SDK from Android Studio tells me that 
everything is ok with my Android configuration, but now with gradle 
instead of ant I can't deploy.
We didn't do any change on the manifest file, so I don't understand the 
issue.


2017-12-09 8:47 GMT+01:00 Nikos Chantziaras >:


You need to edit the Android manifest file, not the pro.user file.
Creator has a special editor dialog for it.



On 09/12/17 02:05, Xavier Bigand wrote:

Hello,

It seems to be a nice version, but I still have some trouble
when targeting Android, with the version 4.4 I had to edit the
.pro.user to make the deployment working by forcing the
BuildTargetSdk at android-26. But now it seems that something
different goes wrong, here is my output:

00:39:06: Le processus
"D:\Softs\SDK\Qt\Tools\mingw530_32\bin\mingw32-make.exe" s'est
terminé normalement.
00:39:06: Starting:
"D:\Softs\SDK\Qt\5.9.3\android_armv7\bin\androiddeployqt.exe"
--input

D:/Dev/Koalabs/HomeDesign3D/Projects/build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Debug/android-libHomeDesign3D.so-deployment-settings.json
--output

D:/Dev/Koalabs/HomeDesign3D/Projects/build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Debug/android-build
--deployment bundled --android-platform android-26 --jdk
"C:/Program Files/Java/jdk1.8.0_112" --gradle
Generating Android Package
    Input file:

D:/Dev/Koalabs/HomeDesign3D/Projects/build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Debug/android-libHomeDesign3D.so-deployment-settings.json
    Output directory:

D:/Dev/Koalabs/HomeDesign3D/Projects/build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Debug/android-build/
    Application binary:

D:/Dev/Koalabs/HomeDesign3D/Projects/build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Debug/libHomeDesign3D.so
    Android build platform: android-26
    Install to device: No
The JavaCompile.setDependencyCacheDir() method has been
deprecated and is scheduled to be removed in Gradle 4.0.
The TaskInputs.source(Object) method has been deprecated and is
scheduled to be removed in Gradle 4.0. Please use
TaskInputs.file(Object).skipWhenEmpty() instead.
:preBuild UP-TO-DATE
:preDebugBuild UP-TO-DATE
:checkDebugManifest
:prepareDebugDependencies
:compileDebugAidl
:compileDebugRenderscript
:generateDebugBuildConfig
:generateDebugResValues
:generateDebugResources
:mergeDebugResources
:processDebugManifest

D:\Dev\Koalabs\HomeDesign3D\Projects\build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Debug\android-build\AndroidManifest.xml:78:5-66
Warning:
Element uses-permission#android.permission.INTERNET at
AndroidManifest.xml:78:5-66 duplicated with element declared at
AndroidManifest.xml:67:9-71

D:\Dev\Koalabs\HomeDesign3D\Projects\build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Debug\android-build\AndroidManifest.xml:80:5-80
Warning:
Element
uses-permission#android.permission.WRITE_EXTERNAL_STORAGE at
AndroidManifest.xml:80:5-80 duplicated with element declared at
AndroidManifest.xml:68:5-81

D:\Dev\Koalabs\HomeDesign3D\Projects\build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Debug\android-build\AndroidManifest.xml:85:5-78
Warning:
Element

Re: [Interest] Can't deploy anymore on QtCretor 4.5

2017-12-09 Thread Xavier Bigand 
Yes, but QtCreator 4.4 had a bug when we get the SDK from Android Studio
instead of the stand alone version that is no more accessible.

QtCreator 4.5 which support the SDK from Android Studio tells me that
everything is ok with my Android configuration, but now with gradle instead
of ant I can't deploy.
We didn't do any change on the manifest file, so I don't understand the
issue.

2017-12-09 8:47 GMT+01:00 Nikos Chantziaras :

> You need to edit the Android manifest file, not the pro.user file. Creator
> has a special editor dialog for it.
>
>
>
> On 09/12/17 02:05, Xavier Bigand wrote:
>
>> Hello,
>>
>> It seems to be a nice version, but I still have some trouble when
>> targeting Android, with the version 4.4 I had to edit the .pro.user to make
>> the deployment working by forcing the BuildTargetSdk at android-26. But now
>> it seems that something different goes wrong, here is my output:
>>
>> 00:39:06: Le processus 
>> "D:\Softs\SDK\Qt\Tools\mingw530_32\bin\mingw32-make.exe"
>> s'est terminé normalement.
>> 00:39:06: Starting: "D:\Softs\SDK\Qt\5.9.3\android
>> _armv7\bin\androiddeployqt.exe" --input D:/Dev/Koalabs/HomeDesign3D/Pr
>> ojects/build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_
>> Qt_5_9_3_for_Android_armv7-Debug/android-libHomeDesign3D.so-deployment-settings.json
>> --output D:/Dev/Koalabs/HomeDesign3D/Projects/build-HomeDesign3D-Andr
>> oid_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Debug/android-build
>> --deployment bundled --android-platform android-26 --jdk "C:/Program
>> Files/Java/jdk1.8.0_112" --gradle
>> Generating Android Package
>>Input file: D:/Dev/Koalabs/HomeDesign3D/Pr
>> ojects/build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_
>> Qt_5_9_3_for_Android_armv7-Debug/android-libHomeDesign3D.so-
>> deployment-settings.json
>>Output directory: D:/Dev/Koalabs/HomeDesign3D/Pr
>> ojects/build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_
>> Qt_5_9_3_for_Android_armv7-Debug/android-build/
>>Application binary: D:/Dev/Koalabs/HomeDesign3D/Pr
>> ojects/build-HomeDesign3D-Android_for_armeabi_v7a_GCC_4_9_
>> Qt_5_9_3_for_Android_armv7-Debug/libHomeDesign3D.so
>>Android build platform: android-26
>>Install to device: No
>> The JavaCompile.setDependencyCacheDir() method has been deprecated and
>> is scheduled to be removed in Gradle 4.0.
>> The TaskInputs.source(Object) method has been deprecated and is scheduled
>> to be removed in Gradle 4.0. Please use 
>> TaskInputs.file(Object).skipWhenEmpty()
>> instead.
>> :preBuild UP-TO-DATE
>> :preDebugBuild UP-TO-DATE
>> :checkDebugManifest
>> :prepareDebugDependencies
>> :compileDebugAidl
>> :compileDebugRenderscript
>> :generateDebugBuildConfig
>> :generateDebugResValues
>> :generateDebugResources
>> :mergeDebugResources
>> :processDebugManifest
>> D:\Dev\Koalabs\HomeDesign3D\Projects\build-HomeDesign3D-Andr
>> oid_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Deb
>> ug\android-build\AndroidManifest.xml:78:5-66 Warning:
>> Element uses-permission#android.permission.INTERNET at
>> AndroidManifest.xml:78:5-66 duplicated with element declared at
>> AndroidManifest.xml:67:9-71
>> D:\Dev\Koalabs\HomeDesign3D\Projects\build-HomeDesign3D-Andr
>> oid_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Deb
>> ug\android-build\AndroidManifest.xml:80:5-80 Warning:
>> Element uses-permission#android.permission.WRITE_EXTERNAL_STORAGE at
>> AndroidManifest.xml:80:5-80 duplicated with element declared at
>> AndroidManifest.xml:68:5-81
>> D:\Dev\Koalabs\HomeDesign3D\Projects\build-HomeDesign3D-Andr
>> oid_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Deb
>> ug\android-build\AndroidManifest.xml:85:5-78 Warning:
>> Element uses-permission#android.permission.ACCESS_NETWORK_STATE at
>> AndroidManifest.xml:85:5-78 duplicated with element declared at
>> AndroidManifest.xml:69:5-79
>> D:\Dev\Koalabs\HomeDesign3D\Projects\build-HomeDesign3D-Andr
>> oid_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Deb
>> ug\android-build\build\intermediates\manifests\full\debug\AndroidManifest.xml:173:28-65:
>> AAPT: No resource found that matches the given name (at 'value' with value
>> '@integer/google_play_services_version').
>> D:\Dev\Koalabs\HomeDesign3D\Projects\build-HomeDesign3D-Andr
>> oid_for_armeabi_v7a_GCC_4_9_Qt_5_9_3_for_Android_armv7-Deb
>> ug\android-build\build\intermediates\manifests\full\debug\AndroidManifest.xml:171:
>> error: Error: No resource found that matches the given name (at 'value'
>> with value '@integer/google_play_services_version').
>>
>>
>> :processDebugResources FAILED
>>
>> FAILURE: Build failed with an exception.
>>
>> * What went wrong:
>> Execution failed for task ':processDebugResources'.
>>  > com.android.ide.common.process.ProcessException: Failed to execute
>> aapt
>>
>> * Try:
>> Run with --stacktrace option to get the stack trace. Run with --info or
>> --debug option to get more log output.
>>
>>
>>
>>
>>
>>
>> Does someone have any idea on how to fix that?
>>
>>
>>
>> --
>>