n said to open xcode for the command line section O.o
Hope this might help other building into a CI like Jenkins the application.
From: Jérôme Godbout
Sent: June 18, 2020 5:25 PM
To: Jérôme Godbout ; Boris Ralchenko
Cc: interest@qt-project.org
Subject: RE: [Interest] Building iOS from command li
painful. Can we just copy an
Info.plist next to the .xcodeproj ? would that be considered by xcode to build
the project?
From: Interest On Behalf Of Jérôme Godbout
Sent: June 18, 2020 4:49 PM
To: Boris Ralchenko
Cc: interest@qt-project.org
Subject: Re: [Interest] Building iOS from command line
: interest@qt-project.org
Subject: Re: [Interest] Building iOS from command line
I do have the bundle ID specified explicitly in the Info.plist.
I prefer Xcode for debugging/packaging. It appears to be more efficient way
when I needed to figure out command line build, less tools to take care of. It
> I was guessing the replacement should have happen. or does the above
> variables only work when inside QtCreator GUI?
>
>
> From: Boris Ralchenko mailto:bralche...@ics.com>>
> Sent: June 18, 2020 2:46 PM
> To: Jérôme Godbout mailto:godbo...@amotus.ca>>
&g
es
only work when inside QtCreator GUI?
From: Boris Ralchenko
Sent: June 18, 2020 2:46 PM
To: Jérôme Godbout
Cc: interest@qt-project.org
Subject: Re: [Interest] Building iOS from command line
Hi Jérôme,
We have a separate Info.plist for command line build, it should solve the
bundle ID issue.
Hi Jérôme,
We have a separate Info.plist for command line build, it should solve the
bundle ID issue. I don’t remember exactly the details, it was couple of years
ago. But I did check - there is an Info.plist in the repository. I suspect Qt
Creator generates one too, but I rely on the one from
Sorry, forgot to mention, the iOS settings when building into the QtCreator is
Development team: Default
Automaticaly manage signing: checked
Qmake setting from within the QtCreators:
additional arguments: is blank (nothing added)
effective calls:
/Users/Shared/Qt/5.15.0/ios/bin/qmake
/Users/MyUS
