2008/12/22 Keith Hubbard <[email protected]>:
>
> It mostly works for me under Leopard (10.5.6).
>
> The first time I tried the build succeeded but no icons were made.
> It turns out the build was using Python from MacPorts which did not
> have PyObjC installed.  I don't know if it is better to hard-code
> the system Python into the script or just document that MacPorts can
> cause problems.  I did not try installing the MacPorts version of
> PyObjC -- it may work fine too.

When you say "no icons were made" you mean that it just created the
MacVim-generic.icns with lots of symlinks to it, or did something else
entirely happen?

Always using the system python sounds good to me.  Can anybody tell me
any reason why I shouldn't call "/usr/bin/python" instead of just
"python"?

> Once I figured out what had happened, I tried again without MacPorts
> in my path.  The icons were not rebuilt automatically, even after
> doing "make distclean", "xcodebuild clean", or blowing away the
> "MacVim/build" directory.  Removing the generated icon files out of
> the source directory worked and so did running the script by hand.

I'm aware of this shortcoming -- I don't know how to automatically
remove the icons on "xcodebuild clean".  Does anybody else know?

Thanks for testing this Keith,
Björn

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to