Thanks. But I don't know how to file abug against QtCreator when it's Xcode not 
doing something.

The good news is I've got an app pending review.

The  only other comments I have is it would be incredibly handy to better 
mention the QMAKE_ variables that are needed for iOS.

Not all of these are documented upfront and need to be searched for. These 
apparently factor into the xcode proj that qmake makes? Otherwise, I was 
expecting to have to check in the xcode project file. I kept changing things in 
Xcode... Explicitly saying these are the variables availible to set specific 
Xcode project settings would be very appreciated. But... I am living the 
cross-platform dream!

ios {
    QMAKE_INFO_PLIST = ios/Info.plist
    QTPLUGIN += qsqlite
    launch_image.files = $$PWD/ios/Launch.xib 
$$files($$PWD/ios/LaunchImage*.png)
    QMAKE_BUNDLE_DATA += launch_images
    ios_icon.files = $$files($$PWD/ios/AppIcon*.png)
    QMAKE_BUNDLE_DATA += ios_icon
    QMAKE_IOS_DEPLOYMENT_TARGET=8.0
    QMAKE_IOS_TARGETED_DEVICE_FAMILY=1,2
}

What is the best way to detect that iOS is the build target? I now have 
platform dependent C++ code. Right now I'm looking at __APPLE__




> Sent: Wednesday, April 08, 2015 at 5:48 AM
> From: "Miettinen Riitta-Leena" <[email protected]>
> To: "Jason H" <[email protected]>, qt-creator <[email protected]>
> Subject: RE: [Qt-creator] Creator iOS woes/feedback
>
> Hello Jason,
> 
> Sorry to hear that your experience with Qt Creator documentation was 
> frustrating. 
> 
> Registering development devices at Apple is not really directly connected 
> with Qt Creator. We added the instructions for one Xcode version (4.6.3) to 
> point developers in the correct direction. But as you said yourself, Apple 
> tends to change things in Xcode and it is not really feasible for us to keep 
> up with them. Therefore, the documentation states the following:
> 
> "The process of configuring devices and the UI varies slightly depending on 
> the Xcode version that you use. The instructions in this section describe the 
> process and UI when using Xcode version 4.6.3."
> (http://doc.qt.io/qtcreator/creator-developing-ios.html)
> 
> Also, the connected state of the device should change to green (connected) 
> after you configure the device using Xcode. Maybe you did that in the 
> meantime and that's what changed the connected state? If you really had to 
> deploy a dummy project (which should not work until the device is connected), 
> that sounds like a bug and it would be great if you could report it.
> 
> For instructions on using Xcode, please read the Xcode documentation or use 
> the Apple channels for support.
> 
> Cheers,
> 
> Leena
> 
> 
> -----Original Message-----
> From: 
> qt-creator-bounces+riitta-leena.miettinen=theqtcompany....@qt-project.org 
> [mailto:qt-creator-bounces+riitta-leena.miettinen=theqtcompany....@qt-project.org]
>  On Behalf Of Jason H
> Sent: Donnerstag, 2. April 2015 16:39
> To: qt-creator
> Subject: [Qt-creator] Creator iOS woes/feedback
> 
> I made a similar post in interest, but this is not that post (though there is 
> some overlap). I want to report the QtCreator specifics.
> Backstory: We've been deploying to android, yesterday I did my first iOS 
> build.
> 
> 1. Instructions for Xcode are wrong. No longer are devices found under Window 
> > Organizer, but Window > Devices. None of the remaining instructions make 
> sense. I've been told by a iOS developer that they keep moving that device 
> screen around Xcode.
> 2. The lack of documentation stating that you need to deploy a dummy project 
> to the device in Xcode. 
>  - This fixed the orange dot and made it green. 
>  - This also set the correct bundle ID (com.XXXX). There seems to be a 
> documented issue with Teams and QtCreator can't select between teams. 
> Originally a test project with another com.YYYY was deployed, Xcode used that 
> initially and complained it wasn't properly provisioned.
> 
> 3. I have no idea where I can set Xcode to point to to control other aspects 
> like LaunchImages and plist stuff.
> 
> 
> Compared to Android the iOS experience is a bit lacking. With android, it's 
> just a manifest, and you provide a handy manifest editor. :-)
> 
> I think a lot of my frustration would have been avoided by more up to date 
> docs. 
> 
> 
> _______________________________________________
> Qt-creator mailing list
> [email protected]
> http://lists.qt-project.org/mailman/listinfo/qt-creator
> 
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator

Reply via email to