Lines Matching +full:xcode +full:- +full:version
6 Jack Jansen (2004-07),
7 Ronald Oussoren (2010-04),
8 Ned Deily (2014-05)
10 :Version: 2.7.15
18 * ``--enable-framework[=DIR]``
22 _`Building and using a framework-based Python on Mac OS X` for more
29 $ ./configure --enable-framework=/Users/ronald/Library/Frameworks
34 command-line tools in ``/Users/ronald/bin``.
36 * ``--with-framework-name=NAME``
39 is only valid when ``--enable-framework`` is specified.
41 * ``--enable-universalsdk[=PATH]``
48 the Xcode default MacOS X SDK, otherwise ``/Developer/SDKs/MacOSX.10.4u.sdk``
52 Line Tools component using ``xcode-select``::
54 $ sudo xcode-select --install
59 * ``--with-universal-archs=VALUE``
62 only valid when ``--enable-universalsdk`` is specified. The default is
63 ``32-bit`` if a building with a SDK that supports PPC, otherwise defaults
71 -----------------------------
75 architecture-specific code into one file and can therefore run at native
77 OS X 10.4 to add support for Intel-based Macs to the existing PowerPC (PPC)
78 machines. In OS X 10.5 support was extended to 64-bit Intel and 64-bit PPC
80 of architectures depending on the build tools and OS X version in use.
83 ------------------------------------
85 You can enable universal binaries by specifying the "--enable-universalsdk"
88 $ ./configure --enable-universalsdk
93 unix build. Universal builds were first supported with OS X 10.4 with Xcode 2.1
94 and the 10.4u SDK. Starting with Xcode 3 and OS X 10.5, more configurations are
98 Apple-supplied compilers and other build tools included in Apple's Xcode
99 development tools. You should install Xcode and the command line tools
108 the default is a 32-bit only binary (i386 and ppc) in build environments that
109 support ppc (10.4 with Xcode 2, 10.5 and 10.6 with Xcode 3) or an
110 Intel-32/-64-bit binary (i386 and X86_64) in build environments that do not
111 support ppc (Xcode 4 on 10.6 and later systems). The flavor can be specified
112 using the configure option ``--with-universal-archs=VALUE``. The following
117 * ``intel-32``: ``i386``
119 * ``intel-64``: ``x86_64``
121 * ``32-bit``: ``ppc``, ``i386``
123 * ``3-way``: ``i386``, ``x86_64``, ``ppc``
125 * ``64-bit``: ``ppc64``, ``x86_64``
129 To build a universal binary that includes a 64-bit architecture, you must build
130 on a system running OS X 10.5 or later. The ``all`` and ``64-bit`` flavors can
132 OS X 10.5. Although legacy ``ppc`` support was included with Xcode 3 on OS X
133 10.6, it was removed in Xcode 4, versions of which were released on OS X 10.6
135 following combinations of SDKs and universal-archs flavors are available:
137 * 10.4u SDK with Xcode 2 supports ``32-bit`` only
139 * 10.5 SDK with Xcode 3.1.x supports all flavors
141 * 10.6 SDK with Xcode 3.2.x supports ``intel``, ``3-way``, and ``32-bit``
143 * 10.6 SDK with Xcode 4 supports ``intel`` only
145 * 10.7 and 10.8 SDKs with Xcode 4 support ``intel`` only
147 * 10.8 and 10.9 SDKs with Xcode 5 support ``intel`` only
149 The makefile for a framework build will also install ``python2.7-32``
150 binaries when the universal architecture includes at least one 32-bit
151 architecture (that is, for all flavors but ``64-bit``).
158 $ arch -i386 python
160 Or to explicitly run in 32-bit mode, regardless of the machine hardware::
162 $ arch -i386 -ppc python
172 subprocesses also run in 32-bit-mode if the main interpreter does, use
173 a ``python2.7-32`` binary and use the value of ``sys.executable`` as the
176 Building and using a framework-based Python on Mac OS X.
181 --------------------------------------------------------------------------
184 exception of X11/XDarwin-based GUI toolkits all GUI programs need to be run
190 A second reason for using frameworks is that they put Python-related items in
192 "/Applications/Python <VERSION>" where ``<VERSION>`` can be e.g. "3.4",
199 ------------------------------------------------------------------
208 ----------------------------
212 aware, though, that the Cocoa-based AquaTk's supplied starting with OS X
214 installing a newer version before building on OS X 10.6 or later, such as
223 -------------------------------------
225 This directory contains a Makefile that will create a couple of python-related
226 applications (full-blown OS X .app applications, that is) in
227 "/Applications/Python <VERSION>", and a hidden helper application Python.app
235 1. ./configure --enable-framework
242 the applications in ``/Applications/Python <VERSION>`` and the unix tools in
247 by configuring with ``--enable-framework=$HOME/Library/Frameworks``.
249 at ``$HOME/Applications/Python-<VERSION>`` and ``$HOME/bin``.
252 frameworkinstall is composed of a couple of sub-targets that install the
257 "/Applications/Python <VERSION>", this is useful for binary
267 double-click a .py, .pyc or .pyw file. For the first two it creates a Terminal
268 window and runs the scripts with the normal command-line Python. For the
270 GUI-things. Keep the ``Option`` key depressed while dragging or double-clicking
275 and out comes a full-featured Mac OS X application. "Build Applet.app" is now
276 deprecated and has been removed in Python 3. As of OS X 10.8, Xcode 4 no
293 ``build-installer.py`` that does all the work. This will download and build
294 a number of 3rd-party libaries, configures and builds a framework Python,
302 script on Mac OS X 10.4 or later and with Xcode 2.1 or later installed.
305 additional software beyond what is provided with Xcode 2. OS X 10.5
308 versions of Xcode to build installers that are compatible with older systems
313 minimum OS X version supported.
320 command-line arguments, run it with --help for more information.
333 configure: WARNING: ## -------------------------------------- ##
335 configure: WARNING: ## -------------------------------------- ##
351 of Python, if you want to remove just one version you have to remove the
352 version-specific subdirectory: ``/Library/Frameworks/Python.framework/Versions/X.Y``.
354 is a symlink that points to an installed version of Python.
367 * http://www.python.org/community/sigs/current/pythonmac-sig/