One click deploy for iOS

[volzhs]

I saw somewhere @reduz tried to find a way to implement one click deploy for ios.
But, it is not done yet and I leave it here for future task.

[reduz]

punto wrote the ios port and he was pretty close

On Thu, Oct 29, 2015 at 11:07 PM, volzhs [email protected] wrote:

I saw somewhere @reduz https://github.com/reduz tried to find a way to
implement one click deploy for ios.
But, it is not done yet and I leave it here for future task.

—
Reply to this email directly or view it on GitHub
#2703.

[romulox-x]

Was this going to tell xcode what to do, or use the new 3rd party stuff?

[punto-]

What is the new 3rd part stuff? If it's reliable (ie Apple is ok with it,
and we don't run the risk of an update that leaves people without the
ability to publish until we fix it) we should use it.. Otherwise I'd say
output an xcode project that can run in debug using the unpackaged project
directory (with the "godot_path" parameter on info.plist), and can also
produce the ipa using the exported data.pck.

On 30 October 2015 at 17:58, romulox-x [email protected] wrote:

Was this going to tell xcode what to do, or use the new 3rd party stuff?

—
Reply to this email directly or view it on GitHub
#2703 (comment).

[romulox-x]

I haven't used the osxcross stuff, but it seems to have been added here: b0aa49a

I share your concerns about reliability. I don't know the answers to those questions, but I wouldn't be surprised if those turned out to be problems at some point. This may work flawlessly today, but I'd be afraid of it breaking any time I installed updates on my Mac. Maybe a "use at your own risk" warning somewhere would be appropriate?

[volzhs]

I think current way is good enough.
But it will be better if it's possible. :)

[reduz]

if punto can't do this, I will give it a check for 2.1

[beocat]

Not sure where this is going but I just noticed a couple of devblog posts from the guys behind Mini Metro about automated build and deploy to connected iphones. Seems to me that the building blocks are there to do the same with Godot, although it requires you to install cfgutil.

http://devlog.dinopoloclub.com/post/138142530760/automated-ios-deployment
http://devlog.dinopoloclub.com/post/138239717055/local-ios-deployment

I might be able to help although I don't really know where to begin - or exactly where we want to end with iOS build and deployment.

[reduz]

This is pretty cool, I was thinking of working on this this month

On Mon, May 16, 2016 at 10:27 AM, beocat [email protected] wrote:

Not sure where this is going but I just noticed a couple of devblog posts
from the guys behind Mini Metro about automated build and deploy to
connected iphones. Seems to me that the building blocks are there to do the
same with Godot, although it requires you to install cfgutil.

http://devlog.dinopoloclub.com/post/138142530760/automated-ios-deployment
http://devlog.dinopoloclub.com/post/138239717055/local-ios-deployment

I might be able to help although I don't really know where to begin - or
exactly where we want to end with iOS build and deployment.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#2703 (comment)

[akien-mga]

Not critical for the upcoming 2.1, so moving to the next milestone. (Though it would be pretty cool to have in 2.1 if @punto- or @reduz can have a closer look at it)

[akien-mga]

Moving to the next milestone as 3.1 is now feature frozen.

[akien-mga]

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.

The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.

If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!