Commit Graph

7 Commits

Author SHA1 Message Date
Ned Deily 22ee4c47ff Issue #22471: Avoid Python Launcher.app install problems by removing
vestigial Makefile step.
2014-09-23 12:48:16 -07:00
Ronald Oussoren 01d149fc1f Fix for issue #3646: with this patch it is possible to do a
framework install of Python in your home directory (on OSX):

   $ configure --enable-framework=${HOME}/Library/Frameworks
   $ make && make install

Without this patch the framework would get installed just fine,
but 'make install' would try to install the application bundles
and command-line tools outside the user's home, which doesn't work
for non-admin users (and is bad form anyway).
2010-04-30 11:20:14 +00:00
Ronald Oussoren 1bf02022fe The PythonLauncher change is needed due
to changes in how the BASECFLAGS and CFLAGS
variables get filled by configure.

The Mac/Makefile.in change ensures that
pythonw gets build with the rigth deployment
targets.
2010-04-20 08:53:12 +00:00
Ronald Oussoren 862359e2e6 Fix for issue 3433 2009-01-02 11:46:05 +00:00
Ronald Oussoren 85f19709f9 Finish fix for issue2573, previous patch was incomplete. 2008-05-02 19:58:56 +00:00
Ronald Oussoren 750e92043e - Patch the correct version of python in the Info.plists at build time, instead
of relying on a maintainer to update them before releases.
- Remove the now empty Mac/OSX directory
2006-06-07 19:38:53 +00:00
Ronald Oussoren c629be8a1e Move Mac/OSX/PythonLauncher one level up 2006-06-07 18:58:01 +00:00