A “built distribution” is what you’re probably used to thinking of either as a“binary package” or an “installer” (depending on your background). It’s notnecessarily binary, though, because it might contain only Python source codeand/or byte-code; and we don’t call it a package, because that word is alreadyspoken for in Python. (And “installer” is a term specific to the world ofmainstream desktop systems.)

GarageBand is a music creation studio that is present on your Mac. If you are wondering how to use GarageBand on Mac, then read this thorough guide that will tell you all the details if you are using the application for the very first time.We’ll guide you on how to download GarageBand from the Apple Store, how to install it and how to get started with this digital audio workstation (DAW). Working with mac tools was good.The company it self very good at first but they kept changing presidents and then when that didn't work they worked there way through management. That kept hurting the guys on the street.

A built distribution is how you make life as easy as possible for installers ofyour module distribution: for users of RPM-based Linux systems, it’s a binaryRPM; for Windows users, it’s an executable installer; for Debian-based Linuxusers, it’s a Debian package; and so forth. Obviously, no one person will beable to create built distributions for every platform under the sun, so theDistutils are designed to enable module developers to concentrate on theirspecialty—writing code and creating source distributions—while anintermediary species called packagers springs up to turn source distributionsinto built distributions for as many platforms as there are packagers.

Of course, the module developer could be their own packager; or the packager couldbe a volunteer “out there” somewhere who has access to a platform which theoriginal developer does not; or it could be software periodically grabbing newsource distributions and turning them into built distributions for as manyplatforms as the software has access to. Regardless of who they are, a packageruses the setup script and the bdist command family to generate builtdistributions.

As a simple example, if I run the following command in the Distutils sourcetree:

then the Distutils builds my module distribution (the Distutils itself in thiscase), does a “fake” installation (also in the build directory), andcreates the default type of built distribution for my platform. The defaultformat for built distributions is a “dumb” tar file on Unix, and a simpleexecutable installer on Windows. (That tar file is considered “dumb” because ithas to be unpacked in a specific location to work.)

Thus, the above command on a Unix system createsDistutils-1.0.plat.tar.gz; unpacking this tarball from the right placeinstalls the Distutils just as though you had downloaded the source distributionand run pythonsetup.pyinstall. (The “right place” is either the root ofthe filesystem or Python’s prefix directory, depending on the optionsgiven to the bdist_dumb command; the default is to make dumbdistributions relative to prefix.)

Obviously, for pure Python distributions, this isn’t any simpler than justrunning pythonsetup.pyinstall—but for non-pure distributions, whichinclude extensions that would need to be compiled, it can mean the differencebetween someone being able to use your extensions or not. And creating “smart”built distributions, such as an RPM package or an executable installer forWindows, is far more convenient for users even if your distribution doesn’tinclude any extensions.

The bdist command has a --formats option, similar to thesdist command, which you can use to select the types of builtdistribution to generate: for example,

would, when run on a Unix system, create Distutils-1.0.plat.zip—again, this archive would be unpacked from the root directory to install theDistutils.

The available formats for built distributions are:

Notes:

1. default on Unix

2. default on Windows

3. requires external utilities: tar and possibly one of gzip,bzip2, or compress

4. requires either external zip utility or zipfile module (partof the standard Python library since Python 1.6)

5. requires external rpm utility, version 3.0.4 or better (use rpm--version to find out which version you have)

You don’t have to use the bdist command with the --formatsoption; you can also use the command that directly implements the format you’reinterested in. Some of these bdist “sub-commands” actually generateseveral similar formats; for instance, the bdist_dumb commandgenerates all the “dumb” archive formats (tar, ztar, gztar, andzip), and bdist_rpm generates both binary and source RPMs. Thebdist sub-commands, and the formats generated by each, are:

The following sections give details on the individual bdist_*commands.

5.1. Creating dumb built distributions¶

5.2. Creating RPM packages¶

The RPM format is used by many popular Linux distributions, including Red Hat,SuSE, and Mandrake. If one of these (or any of the other RPM-based Linuxdistributions) is your usual environment, creating RPM packages for other usersof that same distribution is trivial. Depending on the complexity of your moduledistribution and differences between Linux distributions, you may also be ableto create RPMs that work on different RPM-based distributions.

The usual way to create an RPM of your module distribution is to run thebdist_rpm command:

or the bdist command with the --format option:

The former allows you to specify RPM-specific options; the latter allows you toeasily specify multiple formats in one run. If you need to do both, you canexplicitly specify multiple bdist_* commands and their options:

Creating RPM packages is driven by a .spec file, much as using theDistutils is driven by the setup script. To make your life easier, thebdist_rpm command normally creates a .spec file based on theinformation you supply in the setup script, on the command line, and in anyDistutils configuration files. Various options and sections in the.spec file are derived from options in the setup script as follows:

Additionally, there are many options in .spec files that don’t havecorresponding options in the setup script. Most of these are handled throughoptions to the bdist_rpm command as follows:

Obviously, supplying even a few of these options on the command-line would betedious and error-prone, so it’s usually best to put them in the setupconfiguration file, setup.cfg—see section Writing the Setup Configuration File. Ifyou distribute or package many Python module distributions, you might want toput options that apply to all of them in your personal Distutils configurationfile (~/.pydistutils.cfg). If you want to temporarily disablethis file, you can pass the –no-user-cfg option to setup.py.

There are three steps to building a binary RPM package, all of which arehandled automatically by the Distutils:

1. create a .spec file, which describes the package (analogous to theDistutils setup script; in fact, much of the information in the setup scriptwinds up in the .spec file)

   Sep 30, 2015 - Explore MaesCHughes's board 'Star Wars nose art' on Pinterest. See more ideas about Nose art, Star wars ships and Star wars art. DeviantArt is the world's largest online social community for artists and art enthusiasts, allowing people to connect through the creation and sharing of art. Star Wars: Togruta Gunship Nose Art by.Offworldtrooper on deviantART. Feb 13, 2020 - Explore cct78260's board 'Gunship nose' on Pinterest. See more ideas about Nose art, Star wars art and Star wars clone wars.

2. create the source RPM

3. create the “binary” RPM (which may or may not contain binary code, dependingon whether your module distribution contains Python extensions)

Normally, RPM bundles the last two steps together; when you use the Distutils,all three steps are typically bundled together.

If you wish, you can separate these three steps. You can use the--spec-only option to make bdist_rpm just create the.spec file and exit; in this case, the .spec file will bewritten to the “distribution directory”—normally dist/, butcustomizable with the --dist-dir option. (Normally, the .specfile winds up deep in the “build tree,” in a temporary directory created bybdist_rpm.)

5.3. Creating Windows Installers¶

Executable installers are the natural format for binary distributions onWindows. They display a nice graphical user interface, display some informationabout the module distribution to be installed taken from the metadata in thesetup script, let the user select a few options, and start or cancel theinstallation.

Since the metadata is taken from the setup script, creating Windows installersis usually as easy as running:

or the bdist command with the --formats option:

If you have a pure module distribution (only containing pure Python modules andpackages), the resulting installer will be version independent and have a namelike foo-1.0.win32.exe. These installers can even be created on Unixplatforms or Mac OS X.

If you have a non-pure distribution, the extensions can only be created on aWindows platform, and will be Python version dependent. The installer filenamewill reflect this and now has the form foo-1.0.win32-py2.0.exe. Youhave to create a separate installer for every Python version you want tosupport.

The installer will try to compile pure modules into bytecode after installationon the target system in normal and optimizing mode. If you don’t want this tohappen for some reason, you can run the bdist_wininst command withthe --no-target-compile and/or the --no-target-optimizeoption.

By default the installer will display the cool “Python Powered” logo when it isrun, but you can also supply your own 152x261 bitmap which must be a Windows.bmp file with the --bitmap option.

The installer will also display a large title on the desktop background windowwhen it is run, which is constructed from the name of your distribution and theversion number. This can be changed to another text by using the--title option.

The installer file will be written to the “distribution directory” — normallydist/, but customizable with the --dist-dir option.

5.4. Cross-compiling on Windows¶

Starting with Python 2.6, distutils is capable of cross-compiling betweenWindows platforms. In practice, this means that with the correct toolsinstalled, you can use a 32bit version of Windows to create 64bit extensionsand vice-versa.

To build for an alternate platform, specify the --plat-name optionto the build command. Valid values are currently ‘win32’, ‘win-amd64’ and‘win-ia64’. For example, on a 32bit version of Windows, you could execute:

to build a 64bit version of your extension. The Windows Installers alsosupport this option, so the command:

would create a 64bit installation executable on your 32bit version of Windows.

To cross-compile, you must download the Python source code and cross-compilePython itself for the platform you are targeting - it is not possible from abinary installation of Python (as the .lib etc file for other platforms arenot included.) In practice, this means the user of a 32 bit operatingsystem will need to use Visual Studio 2008 to open thePCBuild/PCbuild.sln solution in the Python source tree and build the“x64” configuration of the ‘pythoncore’ project before cross-compilingextensions is possible.

Note that by default, Visual Studio 2008 does not install 64bit compilers ortools. You may need to reexecute the Visual Studio setup process and selectthese tools (using Control Panel->[Add/Remove] Programs is a convenient way tocheck or modify your existing install.)

5.4.1. The Postinstallation script¶

Starting with Python 2.3, a postinstallation script can be specified with the--install-script option. The basename of the script must bespecified, and the script filename must also be listed in the scripts argumentto the setup function.

This script will be run at installation time on the target system after all thefiles have been copied, with argv[1] set to -install, and again atuninstallation time before the files are removed with argv[1] set to-remove.

The installation script runs embedded in the windows installer, every output(sys.stdout, sys.stderr) is redirected into a buffer and will bedisplayed in the GUI after the script has finished.

Some functions especially useful in this context are available as additionalbuilt-in functions in the installation script.

These functions should be called when a directory or file is created by thepostinstall script at installation time. It will register path with theuninstaller, so that it will be removed when the distribution is uninstalled.To be safe, directories are only removed if they are empty.

This function can be used to retrieve special folder locations on Windows likethe Start Menu or the Desktop. It returns the full path to the folder.csidl_string must be one of the following strings:

If the folder cannot be retrieved, OSError is raised.

Which folders are available depends on the exact Windows version, and probablyalso the configuration. For details refer to Microsoft’s documentation of theSHGetSpecialFolderPath() function.

This function creates a shortcut. target is the path to the program to bestarted by the shortcut. description is the description of the shortcut.filename is the title of the shortcut that the user will see. argumentsspecifies the command line arguments, if any. workdir is the working directoryfor the program. iconpath is the file containing the icon for the shortcut,and iconindex is the index of the icon in the file iconpath. Again, fordetails consult the Microsoft documentation for the IShellLinkinterface.

5.5. Vista User Access Control (UAC)¶

Starting with Python 2.6, bdist_wininst supports a --user-access-controloption. The default is ‘none’ (meaning no UAC handling is done), and othervalid values are ‘auto’ (meaning prompt for UAC elevation if Python wasinstalled for all users) and ‘force’ (meaning always prompt for elevation).

Devices and Mac OS X version

VLC media player requires Mac OS X 10.7.5 or later. It runs on any 64bit Intel-based Mac. Previous devices are supported by older releases.
Note that the first generation of Intel-based Macs equipped with Core Solo or Core Duo processors is no longer supported. Please use version 2.0.10 linked below.

Web browser plugin for Mac OS X

Support for NPAPI plugins was removed from all modern web browsers, so VLC's plugin is no longer maintained. The last version is 3.0.4 and can be found here. It will not receive any further updates.

Older versions of Mac OS X and VLC media player

We provide older releases for users who wish to deploy our software on legacy releases of Mac OS X. You can find recommendations for the respective operating system version below. Note that support ended for all releases listed below and hence they won't receive any further updates.

Mac OS X 10.6 Snow Leopard

Use VLC 2.2.8. Get it here.

Mac OS X 10.5 Leopard

Use VLC 2.0.10. Get it for PowerPC or 32bit Intel.

Mac OS X 10.4 Tiger

Mac OS X 10.4.7 or later is required

Use VLC 0.9.10. Get it for PowerPC or Intel.

Mac OS X 10.3 Panther

QuickTime 6.5.2 or later is required

Use VLC 0.8.6i. Get it for PowerPC.

Mac OS X 10.2 Jaguar

Use VLC 0.8.4a. Get it for PowerPC.

Mac OS X 10.0 Cheetah and 10.1 Puma

Use VLC 0.7.0. Get it for PowerPC.