* Don't use xcodebuild for building PythonLauncher, but use a normal unix
  makefile. This makes it a lot easier to use the same build flags as for the
  rest of python (e.g. make a universal version of python launcher)
* Convert the mac makefile-s to makefile.in-s and use configure to set makefile
  variables instead of forwarding them as command-line arguments
* Add a C version of pythonw, that we you can use '#!/usr/local/bin/pythonw'
* Build IDLE.app using bundlebuilder instead of BuildApplet, that will allow
  easier modification of the bundle contents later on.

option to various tools, and do the right thing when we're doing a destroot
install.

Will backport to 2.4 and 2.3.

until now: the inheritance of default values was the wrong way around.
This caused app bundles to get a type of "BNDL" instead of "APPL".
Apparently this is not a problem until you try to drag your app to
the dock.
----------------------------------------------------------------------

- added bundle_id/--bundle-id option, to specify the CFBundleIndentifier
#765615:
- in the appropriate situation, prepend $PATH with our path instead of
  setting it.

line also use this as the executable in the bundle.

- don't use "abc" in aString
- don't reorganize extension modules when not using zipimport

  installed Python, yet include any modules not in the std lib
- reworked extension module inclusion code: put all .so files in
  a subdirectory of Contents/Resources/, but more importantly,
  correctly support extensions that are submodules.

- move the normpath stuff around a bit
- added dubious special case to addPythonFramework()

executable in the bundle. Therefore got rid of the "binaries" attribute.

in the bootstrap script of the applet.

frameworks to the bundle.

except to avoid getpath.c giving unsollicited advice on stderr.

AppBuilder, and set the default type to BNDL (overridden in AppBuilder).

This surfaced when trying to build help bundles.

is now in buildtools.

- tweaked the help text a little.
(Jack: up to you to change your client code.)

- Replaced bootstrap shell script with Python script. This means
  standalone apps built with bundlebuilder will not work on MacOS < 10.1,
  since we depend (again) on an installed Python.
- Add a hack to set sys.executable; the bootstrap script does os.execve()
  with an argv[0] that's different from the actual Python executable
  (it has to match the CFBundleExecutable entry in the Info.plist to make
  the app work both from the Finder and the command line, and it has to be
  the bootstrap script), yet a proper sys.executable is needed to spawn
  auxiliary processes.

into dst in the bundle. The Python API already had this functionality

creates the sys.argv emulation wrapper for droplets. Also updates
the plist, if needed, and the includedModules (but this last is untested).

arguments, and also does the right thing for the no argument case.

"copy anything to a data fork based resource file" trick of macresource.
Fixes #688007.

This work uncovered the zipimport bug in 2.3a1 -- wish I'd had time to
do this before the release :-(.

in MacPython-OS9 and MacPython-OSX (or the equivalent unix Python on
Mac OS X). The only items remaining in Mac/Lib are modules that are
meaningful only for MacPython-OS9 (CFM stuff, MacPython preferences
in resources, etc).