Include a PYTHONPATH extension allowing for user-space packages.

Briefcase macOS Xcode Template

A Cookiecutter template for building Python apps that will run under macOS.

Using this template

The easiest way to use this project is to not use it at all - at least, not directly. Briefcase is a tool that uses this template, rolling it out using data extracted from a pyproject.toml configuration file.

However, if you do want use this template directly...

Install cookiecutter. This is a tool used to bootstrap complex project templates:
```
$ pip install cookiecutter
```
Run cookiecutter on the template:
```
$ cookiecutter https://github.com/beeware/briefcase-macOS-Xcode-template
```
This will ask you for a number of details of your application, including the name of your application (which should be a valid PyPI identifier), and the Formal Name of your application (the full name you use to describe your app). The remainder of these instructions will assume a name of my-project, and a formal name of My Project.
Obtain a Python Apple support package for macOS, and extract it into the My Project/Support directory generated by the template.
Add your code to the template, into the My Project/My Project/app. directory. At the very minimum, you need to have an app/<app name>/__main__.py file that will be run on startup.

If your code has any dependencies, they should be installed into the My Project/My Project/app_packages directory.

If you've done this correctly, a project with a formal name of My Project, with an app name of my-project should have a directory structure that looks something like:

My Project/
    My Project/
        app/
            my_project/
                __init__.py
                app.py
        app_packages/
            ...
        ...
    My Project.xcodeproj/
        ...
    Support/
        ...
        VERSIONS
    briefcase.toml

You're now ready to open the XCode project file, build and run your project!

Next steps

Of course, running Python code isn't very interesting by itself - you'll be able to output to the console, and see that output in XCode, but if you tap the app icon on your phone, you won't see anything - because there isn't a visible console on an iPhone.

To do something interesting, you'll need to work with the native macOS system libraries to draw widgets and respond to screen taps. The Rubicon Objective C bridging library can be used to interface with the macOS system libraries. Alternatively, you could use a cross-platform widget toolkit that supports macOS (such as Toga) to provide a GUI for your application.

Regardless of whether you use Toga, or you write an application natively, the template project will try to start a Python module matching the name of the MainModule property in the Info.plist file associated with the project. If that module can't be started, any error raised will be logged, and the Python interpreter will be shut down. All console output and errors are automatically redirected to the macOS system console.

If you have any external library dependencies (like Toga, or anything other third-party library), you should install the library code into the app_packages directory. This directory is the same as a site_packages directory on a desktop Python install.

	python_home = [NSString stringWithFormat:@"%@/support/python-stdlib", resourcePath, nil];
	NSLog(@"PythonHome: %@", python_home);
	wtmp_str = Py_DecodeLocale([python_home UTF8String], NULL);
	status = PyConfig_SetString(&config, &config.home, wtmp_str);

	path = [NSString stringWithFormat:@"%@/support/python-stdlib/lib-dynload", resourcePath, nil];
	NSLog(@"- %@", path);
	wtmp_str = Py_DecodeLocale([path UTF8String], NULL);
	status = PyWideStringList_Append(&config.module_search_paths, wtmp_str);

beeware / briefcase-macos-xcode-template Goto Github PK

briefcase-macos-xcode-template's Introduction

Briefcase macOS Xcode Template

Using this template

Next steps

briefcase-macos-xcode-template's People

Contributors

Stargazers

Watchers

Forkers

briefcase-macos-xcode-template's Issues

What is the problem or limitation you are having?

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Describe the bug

Steps to reproduce

Expected behavior

Screenshots

Environment

Logs

Additional context

Recommend Projects

Recommend Topics

Recommend Org