Re: MacVim snapshot 72 for OS X 10.9 (on 10.5 and 10.6)
Am 26.10.2013 um 20:54 schrieb björn: I had another look and managed to avoid using deprecated CGContext.. functions. Check the latest commit in the repo. I build this version on 10.6.8 and it compiles and seems to work fine. (I’m using the Core Text renderer.) Building on 10.5.8 (PPC) failed with: cp -pR MacVim-*.icns /Volumes/Diotima/src/macvim/src/MacVim/build/Release/MacVim.app/Contents/Resources/ ** BUILD FAILED ** The following build commands failed: PSMTabBarControlFramework: CopyTiffFile /Volumes/Diotima/src/macvim/src/MacVim/PSMTabBarControl/../build/Release/PSMTabBarControl.framework/Versions/A/Resources/AquaTabClose_Front_Pressed.tif images/AquaTabClose_Front_Pressed.tif On 10.6.8 I have TIFF Files, on 10.5.8 I only have PNG Files CopyTiffFile /Volumes/Diotima/src/macvim/src/MacVim/PSMTabBarControl/../build/Release/PSMTabBarControl.framework/Versions/A/Resources/AquaTabClose_Front_Rollover.tif images/AquaTabClose_Front_Rollover.tif CopyTiffFile /Volumes/Diotima/src/macvim/src/MacVim/PSMTabBarControl/../build/Release/PSMTabBarControl.framework/Versions/A/Resources/AquaTabClose_Front.tif images/AquaTabClose_Front.tif CopyTiffFile /Volumes/Diotima/src/macvim/src/MacVim/PSMTabBarControl/../build/Release/PSMTabBarControl.framework/Versions/A/Resources/TabIcon.tif images/TabIcon.tif CopyTiffFile /Volumes/Diotima/src/macvim/src/MacVim/PSMTabBarControl/../build/Release/PSMTabBarControl.framework/Versions/A/Resources/TabControlRep.tif images/TabControlRep.tif MacVim: CopyStringsFile /Volumes/Diotima/src/macvim/src/MacVim/build/Release/MacVim.app/Contents/Resources/English.lproj/InfoPlist.strings English.lproj/InfoPlist.strings CopyPlistFile /Volumes/Diotima/src/macvim/src/MacVim/build/Release/MacVim.app/Contents/Resources/Colors.plist Colors.plist CopyPlistFile /Volumes/Diotima/src/macvim/src/MacVim/build/Release/MacVim.app/Contents/Resources/Actions.plist Actions.plist CopyPlistFile /Volumes/Diotima/src/macvim/src/MacVim/build/Release/MacVim.app/Contents/Resources/SystemColors.plist SystemColors.plist CopyPlistFile /Volumes/Diotima/src/macvim/src/MacVim/build/Release/MacVim.app/Contents/Resources/KeyBinding.plist KeyBinding.plist (10 failures) To be sure I re-cloned the repository but the failures remain. When I copy the files manually (taking the tiffs from the 10.6.8 machine) I get a working Vim. On 10.5.8 I have Python 2.5.1, on 10.6.8 I have Python 2.6.1, in case that matters. Axel -- -- You received this message from the vim_mac maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_mac group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Crashing Vim 7.4a9 snapshot 68 with folding
Am 29.07.2013 um 22:15 schrieb Bram Moolenaar: Axel Kielhorn wrote: Update: As I have written earlier, the crash was introduced with Vim 7.3.1185. And here is the RegEx that causes the crash: syn match pandocPCite /@\%[\w\-]*/ It is part of the citation handling code in ~/.vim/syntax/pandoc.vim from vim-pandoc. It doesn't crash for me. It crashes on Mac OS 10.6.8 but not 10.8.4, this may be compiler or library related. What text does it crash on? [@pandoc] in the second line. If you can make it happen with match() that would be ideal. If I start vim with mvim -u NONE -U NONE vimkill3.md and enter (copy) the search string /@\%[\w\-]* I get a crash. without the * it's fine. With incsearch on I get the crash as soon as I type the final * Using /@[a-zA-Z-]* is fine The change was adding *reginput != NUL to regexp_nfa.c (line 3942) Do you have a context diff for this change? Sourcetree gives me Commit: 38388a218e4bc1dbc0475df3d74244034b669b73[38388a2] case NFA_BOL: case NFA_BOF: /* ^ won't match past end-of-line, don't bother trying. -* Except when we are going to the next line for a look-behind -* match. */ +* Except when at the end of the line, or when we are going to the +* next line for a look-behind match. */ if (reginput regline +*reginput != NUL (nfa_endp == NULL || !REG_MULTI || reglnum == nfa_endp-se_u.pos.lnum)) The enclosed file is even more reduced but shows the problem. Axel -- -- You received this message from the vim_mac maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_mac group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. vimkill3.md Description: Binary data
Re: Vim 7.4b ready for beta testing
Am 28.07.2013 um 21:47 schrieb björn: On Sun, Jul 28, 2013 at 6:35 PM, Bram Moolenaar wrote: Hello Vim users, Announcing: Vim (Vi IMproved) version 7.4b BETA Oh dear, this reminds me that I didn't investigate my crashing problem. Well, here it is: Vim 7.3.1184 works fine, 7.3.1185 crashes. The change was adding *reginput != NUL to regexp_nfa.c (line 3942) Axel -- -- You received this message from the vim_mac maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_mac group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Crashing Vim 7.4a9 snapshot 68 with folding
Am 14.07.2013 um 13:02 schrieb Bram Moolenaar: Axel Kielhorn wrote: I usually build Vim from git source but tested the official (Snow Leopard) snapshot as well. I'm on MacOS 10.6.8. My compiler: gcc --version i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3) (I can build on 10.8.4 using current xcode as well.) When using the latest vim-pandoc https://github.com/vim-pandoc/vim-pandoc I can crash vim editing the following file: Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 libSystem.B.dylib 0x7fff840e50b6 __kill + 10 1 Vim 0x0001000efa5a mch_exit + 58 2 libSystem.B.dylib 0x7fff840f71ba _sigtramp + 26 3 Vim 0x000100108b8c addstate + 12 4 Vim 0x00010010927a addstate + 1786 5 Vim 0x00010010927a addstate + 1786 [etc.] Looks like recursive use of addstate(). Does it run out of stack? I don't know what _sigtramp is. Could be a bug in the regexp engine. I downloaded snapshot 66 which is Vim 7.3.754 and it doesn't crash. I rebuild Vim 7.3.754 with my current compiler and it crashed. Any idea where to look? The last Xcode update was in March 2011 That was before snapshot 66 was build (2010 Aug 15, compiled Dec 13 2012 00:07:34) Axel -- -- You received this message from the vim_mac maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_mac group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Crashing Vim 7.4a9 snapshot 68 with folding
Another datapoint: I build Vim 7.4a9 on MacOS 10.8 with gcc --version i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00) No problems here. On 10.6 I have gcc --version i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3) Axel -- -- You received this message from the vim_mac maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_mac group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Crashing Vim 7.4a9 snapshot 68 with folding
Am 14.07.2013 um 18:12 schrieb Axel Kielhorn: Another datapoint: I build Vim 7.4a9 on MacOS 10.8 with gcc --version i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00) No problems here. On 10.6 I have gcc --version i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3) And another one: Xcode 3.2.6 (The last version compatible with MacOS 10.6) comes with regular gcc 4.2.1 and llvm-gcc-4.2 --version i686-apple-darwin10-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.6) With ./configure CC=llvm-gcc-4.2 the resulting Vim 7.3.754 does not crash. I'll build 7.4a9 probably tomorrow. Axel -- -- You received this message from the vim_mac maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_mac group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Crashing Vim 7.4a9 snapshot 68 with folding
Am 14.07.2013 um 19:50 schrieb Axel Kielhorn: Am 14.07.2013 um 18:12 schrieb Axel Kielhorn: Another datapoint: I build Vim 7.4a9 on MacOS 10.8 with gcc --version i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00) No problems here. On 10.6 I have gcc --version i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3) And another one: Xcode 3.2.6 (The last version compatible with MacOS 10.6) comes with regular gcc 4.2.1 and llvm-gcc-4.2 --version i686-apple-darwin10-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.6) With ./configure CC=llvm-gcc-4.2 the resulting Vim 7.3.754 does not crash. Build with llvm-gcc-4.2 7.3.1168 works fine 7.3.1184 works fine There are some changes to the regex engine. 7.3.1193 crash 7.3.1214 crash That's definitely all for today, I'm gonna watch football:-) Axel -- -- You received this message from the vim_mac maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_mac group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Bug - Opening files in split window mode
Am 27.08.2012 um 22:57 schrieb Phil S: I downloaded the recommended plug-in and copied it to the plug-in directory in the MacVim package but am still running into the same problem. (I renamed the plugin from .vba to .vim... i assume thats correct). Any other thoughts? .vba means it is a vimball, a kind of vim script installer. You’ll have to download and install vimball first: http://www.vim.org/scripts/script.php?script_id=1502 Axel -- You received this message from the vim_mac maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: Unicode matchpairs not possible?
Am 03.07.2012 um 14:17 schrieb Tony Mechelynck: It is documented under :help 'matchpairs': Currently only single byte character pairs are allowed, and they must be different. Thanks, I somehow missed that. Maybe I should transform » and « to and while editing and convert it back when writing the file. It's easier to type that way, which is another bonus. Axel -- You received this message from the vim_mac maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Unicode matchpairs not possible?
Hi!
I'm using:
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jun 4 2012 19:19:42)
MacOS X (unix) version
Included patches: 1-531
The default matchpairs are:
matchpair(:),{:},[:]
I can
:set mps+=:
to add a new matchpair, but I can't
:set mps+=«:»
or
:set mps+=‹:›
I get
E474: Invalid argument: mps+=‹:›
Shouldn't Vim accept any unicode character?
Axel
--
You received this message from the vim_mac maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
Re: Where do I place fonts?
Am 26.02.2012 um 17:19 schrieb Eric Weir: On Feb 25, 2012, at 4:16 PM, retiredff wrote: On my Mac, any new fonts I put here: ~/Library/Fonts/ I guess I should be more specific. I'm told the gyre fonts are 'open type fonts.' Is this where I should put that that type of font? You are using a Mac, right? Why don't you select all the fonts, right click, open with FontBook. This will give you some windows, one for each font family and an option to install the fonts. In FontBook you can choose whether to install on the computer (=for all users) or for the current user. BTW, you can only use the monospaced fonts with MacVim. Axel -- You received this message from the vim_mac maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: MacVim.app - Snapshot 50
Am 10.10.2009 um 00:27 schrieb björn: Hi, I have uploaded a new snapshot to: http://code.google.com/p/macvim/wiki/Snapshot Builds fine on MacOS 10.5.8 intel. Axel --~--~-~--~~~---~--~~ You received this message from the vim_mac maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Ctrl doesn't work in MacVim (Snow Leopard) with a Swedish Dvorak keyboard layout (linked)...
Am 12.09.2009 um 22:06 schrieb Fredrik Bränström: Uh, wrong file. The .keylayout is located in the .bundle/Contents/ Resources... Attaching the .bundle. I had a look at your keylayout file: There is no mapping table for control. My custom map file has: modifierMap id=commonModifiers defaultIndex=0 keyMapSelect mapIndex=0 modifier keys=/ modifier keys=command anyShift? caps?/ /keyMapSelect keyMapSelect mapIndex=1 modifier keys=anyShift caps?/ /keyMapSelect keyMapSelect mapIndex=2 modifier keys=caps/ /keyMapSelect keyMapSelect mapIndex=3 modifier keys=anyOption/ /keyMapSelect keyMapSelect mapIndex=4 modifier keys=anyShift caps? anyOption/ /keyMapSelect keyMapSelect mapIndex=5 modifier keys=anyShift? caps? anyOption command/ /keyMapSelect keyMapSelect mapIndex=6 modifier keys=anyShift? caps? anyOption? command? anyControl/ /keyMapSelect /modifierMap While you only have modifierMap id=48 defaultIndex=0 keyMapSelect mapIndex=0 modifier keys= / /keyMapSelect keyMapSelect mapIndex=1 modifier keys=anyShift / modifier keys=caps / /keyMapSelect keyMapSelect mapIndex=2 modifier keys=anyOption caps? / /keyMapSelect keyMapSelect mapIndex=3 modifier keys=command anyShift? caps? anyControl? / /keyMapSelect keyMapSelect mapIndex=4 modifier keys=command anyShift? caps? anyOption anyControl? / /keyMapSelect /modifierMap My keymap 6 looks like this: (Warning, this will give you a german keylayout for control if you insert it into your keylayout.) keyMap index=6 !-- control -- key code=0 output=#x0001;/ key code=1 output=#x0013;/ key code=2 output=#x0004;/ key code=3 output=#x0006;/ key code=4 output=#x0008;/ key code=5 output=#x0007;/ key code=6 output=#x001a;/ key code=7 output=#x0018;/ key code=8 output=#x0003;/ key code=9 output=#x0016;/ key code=10 output=0/ key code=11 output=#x0002;/ key code=12 output=#x0011;/ key code=13 output=#x0017;/ key code=14 output=#x0005;/ key code=15 output=#x0012;/ key code=16 output=#x0019;/ key code=17 output=#x0014;/ key code=18 output=1/ key code=19 output=2/ key code=20 output=3/ key code=21 output=4/ key code=22 output=6/ key code=23 output=5/ key code=24 output==/ key code=25 output=9/ key code=26 output=7/ key code=27 output=#x001f;/ key code=28 output=8/ key code=29 output=0/ key code=30 output=#x001d;/ key code=31 output=#x000f;/ key code=32 output=#x0015;/ key code=33 output=#x001b;/ key code=34 output=#x0009;/ key code=35 output=#x0010;/ key code=36 output=#x000d;/ key code=37 output=#x000c;/ key code=38 output=#x000a;/ key code=39 output='/ key code=40 output=#x000b;/ key code=41 output=;/ key code=42 output=#x001c;/ key code=43 output=,/ key code=44 output=// key code=45 output=#x000e;/ key code=46 output=#x000d;/ key code=47 output=./ key code=48 output=#x0009;/ key code=49 output= / key code=50 output=`/ key code=51 output=#x0008;/ key code=52 output=#x0003;/ key code=53 output=#x001b;/ !-- gap, 54 through 64 -- key code=64 output=#x0010;/ key code=65 output=./ key code=66 output=#x001d;/ key code=67 output=*/ !-- gap, 68 -- key code=69 output=+/ key code=70 output=#x001c;/ key code=71 output=#x001b;/ key code=72 output=#x001f;/ !-- gap, 73-74 -- key code=75 output=// key code=76 output=#x0003;/ key code=77 output=#x001e;/ key code=78 output=-/ !-- gap, 79-80 -- key code=79 output=#x0010;/ key code=80 output=#x0010;/ key code=81 output==/ key code=82 output=0/ key code=83 output=1/ key code=84 output=2/
Re: Snow Leopard drops MacOSX10.4u.sdk SDK -- MacVim won't build on 10.6
Am 02.09.2009 um 20:18 schrieb björn: 2009/9/2 Axel Kielhorn: Sorry, please see the attached file. Thanks Axel. The problem was that I used the availability macros incorrectly (MAC_OS_X_VERSION_MAX_ALLOWED etc.) which was just now pointed out to me in a private mail. I've pushed a patch to the repo so MacVim should build on 10.5 again, but please let me know if there are any other problems. ** BUILD SUCCEEDED ** Thank you! Axel --~--~-~--~~~---~--~~ You received this message from the vim_mac maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Snow Leopard drops MacOSX10.4u.sdk SDK -- MacVim won't build on 10.6
Am 02.09.2009 um 03:36 schrieb björn: If anybody builds MacVim on 10.5 or 10.4, please let me know if it still works or if I inadvertently broke something in the process. Note: you will have to reconfigure (./configure ...) and clean the entire project for all the patches to work. I did a make clean and ./configure. gcc -L/usr/local/lib -m32 -o Vim objects/buffer.o objects/ charset.o objects/diff.o objects/digraph.o objects/edit.o objects/ eval.o objects/ex_cmds.o objects/ex_cmds2.o objects/ex_docmd.o objects/ ex_eval.o objects/ex_getln.o objects/fileio.o objects/fold.o objects/ getchar.o objects/hardcopy.o objects/hashtab.o objects/if_cscope.o objects/if_xcmdsrv.o objects/main.o objects/mark.o objects/memfile.o objects/memline.o objects/menu.o objects/message.o objects/misc1.o objects/misc2.o objects/move.o objects/mbyte.o objects/normal.o objects/ops.o objects/option.o objects/os_unix.o objects/pathdef.o objects/popupmnu.o objects/quickfix.o objects/regexp.o objects/ screen.o objects/search.o objects/spell.o objects/syntax.o objects/ tag.o objects/term.o objects/ui.o objects/undo.o objects/window.o objects/gui.o objects/pty.o objects/gui_macvim.o objects/MMBackend.o objects/MacVim.o objects/os_macosx.o objects/os_mac_conv.o objects/netbeans.o objects/version.o -framework Cocoa -framework Carbon -lm -lncurses -liconv -lintl link.sh: Linked OK Looks fine I removed the build folder from MacVIm xcodebuild leads to: he following build commands failed: PSMTabBarControlFramework: CompileC ../build/PSMTabBarControl.build/Release/ PSMTabBarControlFramework.build/Objects-normal/i386/ PSMOverflowPopUpButton.o /Users/axel/src/MacVim/src/MacVim/ PSMTabBarControl/source/PSMOverflowPopUpButton.m normal i386 objective- c com.apple.compilers.gcc.4_0 CompileC ../build/PSMTabBarControl.build/Release/ PSMTabBarControlFramework.build/Objects-normal/i386/ PSMTabBarControl.o /Users/axel/src/MacVim/src/MacVim/PSMTabBarControl/ source/PSMTabBarControl.m normal i386 objective-c com.apple.compilers.gcc.4_0 CompileC ../build/PSMTabBarControl.build/Release/ PSMTabBarControlFramework.build/Objects-normal/i386/PSMTabBarCell.o / Users/axel/src/MacVim/src/MacVim/PSMTabBarControl/source/ PSMTabBarCell.m normal i386 objective-c com.apple.compilers.gcc.4_0 CompileC ../build/PSMTabBarControl.build/Release/ PSMTabBarControlFramework.build/Objects-normal/i386/PSMAquaTabStyle.o / Users/axel/src/MacVim/src/MacVim/PSMTabBarControl/source/ PSMAquaTabStyle.m normal i386 objective-c com.apple.compilers.gcc.4_0 CompileC ../build/PSMTabBarControl.build/Release/ PSMTabBarControlFramework.build/Objects-normal/i386/ PSMMetalTabStyle.o /Users/axel/src/MacVim/src/MacVim/PSMTabBarControl/ source/PSMMetalTabStyle.m normal i386 objective-c com.apple.compilers.gcc.4_0 CompileC ../build/PSMTabBarControl.build/Release/ PSMTabBarControlFramework.build/Objects-normal/i386/ PSMProgressIndicator.o /Users/axel/src/MacVim/src/MacVim/ PSMTabBarControl/source/PSMProgressIndicator.m normal i386 objective-c com.apple.compilers.gcc.4_0 CompileC ../build/PSMTabBarControl.build/Release/ PSMTabBarControlFramework.build/Objects-normal/i386/ PSMTabDragAssistant.o /Users/axel/src/MacVim/src/MacVim/ PSMTabBarControl/source/PSMTabDragAssistant.m normal i386 objective-c com.apple.compilers.gcc.4_0 CompileC ../build/PSMTabBarControl.build/Release/ PSMTabBarControlFramework.build/Objects-normal/i386/ PSMUnifiedTabStyle.o /Users/axel/src/MacVim/src/MacVim/ PSMTabBarControl/source/PSMUnifiedTabStyle.m normal i386 objective-c com.apple.compilers.gcc.4_0 MacVim: CompileC build/MacVim.build/Release/MacVim.build/Objects-normal/i386/ MMAppController.o /Users/axel/src/MacVim/src/MacVim/MMAppController.m normal i386 objective-c com.apple.compilers.gcc.4_0 CompileC build/MacVim.build/Release/MacVim.build/Objects-normal/i386/ MMTextView.o /Users/axel/src/MacVim/src/MacVim/MMTextView.m normal i386 objective-c com.apple.compilers.gcc.4_0 CompileC build/MacVim.build/Release/MacVim.build/Objects-normal/i386/ MMVimController.o /Users/axel/src/MacVim/src/MacVim/MMVimController.m normal i386 objective-c com.apple.compilers.gcc.4_0 CompileC build/MacVim.build/Release/MacVim.build/Objects-normal/i386/ MMWindowController.o /Users/axel/src/MacVim/src/MacVim/ MMWindowController.m normal i386 objective-c com.apple.compilers.gcc.4_0 CompileC build/MacVim.build/Release/MacVim.build/Objects-normal/i386/ MMFullscreenWindow.o /Users/axel/src/MacVim/src/MacVim/ MMFullscreenWindow.m normal i386 objective-c com.apple.compilers.gcc.4_0 CompileC build/MacVim.build/Release/MacVim.build/Objects-normal/i386/ MMVimView.o /Users/axel/src/MacVim/src/MacVim/MMVimView.m normal i386 objective-c com.apple.compilers.gcc.4_0 CompileC build/MacVim.build/Release/MacVim.build/Objects-normal/i386/
Re: Snow Leopard drops MacOSX10.4u.sdk SDK -- MacVim won't build on 10.6
Am 02.09.2009 um 18:03 schrieb björn: 2009/9/2 Axel Kielhorn: Am 02.09.2009 um 03:36 schrieb björn: If anybody builds MacVim on 10.5 or 10.4, please let me know if it still works or if I inadvertently broke something in the process. Note: you will have to reconfigure (./configure ...) and clean the entire project for all the patches to work. I removed the build folder from MacVIm xcodebuild leads to: -snip- Uh, where is the actual error? The output from xcodebuild is semi-impossible to read but as far as I can tell that output did not include the error messages. It may help if you open Xcode and build from there, then look in the build window (Cmd-Shift-b). Sorry, please see the attached file. Axel --~--~-~--~~~---~--~~ You received this message from the vim_mac maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~--- build.log Description: Binary data
