orestis | 1 Oct 2009 02:11
Picon

Re: Simplified build procedure for MacVim


Hello Björn,

I am trying to build the latest version from git, but i keep getting
errors at the creation of the icons.

The commands i use to build are:

    ./configure --enable-cscope \
                      --with-macsdk=10.5
     make

This is the output i get:
....
# "now", so that the zip is not unzipped in every `make` run.`
touch Envy\ Code\ R\ Bold.ttf
make -C makeicns
cc -fpascal-strings -O2   -c -o makeicns.o makeicns.m
cc -fpascal-strings -O2   -c -o IconFamily.o IconFamily.m
cc -fpascal-strings -O2   -c -o NSString+CarbonFSRefCreation.o NSString
+CarbonFSRefCreation.m
g++ -o makeicns makeicns.o IconFamily.o NSString+CarbonFSRefCreation.o
-O2 \
	  -framework Foundation -framework AppKit -framework Carbon
/usr/bin/python make_icons.py /Users/orestis/Code/macvim-build/src/
MacVim/build/Release/MacVim.app/Contents/Resources
MacVim-cpp
Command /bin/sh failed with exit code 2
Command /bin/sh failed with exit code 2
Touch build/Release/MacVim.app
(Continue reading)

björn | 1 Oct 2009 11:25
Picon
Gravatar

Re: Simplified build procedure for MacVim


2009/10/1 orestis:
>
> I am trying to build the latest version from git, but i keep getting
> errors at the creation of the icons.
>
> The commands i use to build are:
>
>    ./configure --enable-cscope \
>                      --with-macsdk=10.5
>     make
>
> This is the output i get:
> ....
>  File "/Users/orestis/Code/macvim-build/src/MacVim/icons/
> docerator.py", line 253, in splitGenericDocumentIcon
>    assert ir == ig == ib
> AssertionError
> make: *** [MacVim-generic.icns] Error 1

Hi Orestis,

That looks like the bug that Nico patched just recently.  Go into
src/MacVim/icons and do a "make clean" and everything should be fine
(you did remember to "git pull", right?).

Björn

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
(Continue reading)

orestis | 1 Oct 2009 12:23
Picon

Re: Simplified build procedure for MacVim


Hello Björn,

Thanks for the reply. I have already tried cleaning the directory
before running make and i still got the same error (sorry for
forgetting to mention it).
I even deleted my local repository and re-pulled it to ensure that i
have a clean one before building and the same problem keeps popping
up.

Whatever i do, it seems that the assertion is always triggered.

By the way, i don't know if this affects anything (probably not), but
i am running the Snow Leopard kernel in 32bit mode.

Thanks,
Orestis

On Oct 1, 10:25 am, björn <bjorn.winck...@...> wrote:
> 2009/10/1 orestis:
>
>
>
>
>
> > I am trying to build the latest version from git, but i keep getting
> > errors at the creation of the icons.
>
> > The commands i use to build are:
>
(Continue reading)

Michael Wookey | 1 Oct 2009 13:12
Picon

Re: Simplified build procedure for MacVim


2009/10/1 orestis <arestis@...>:
> I even deleted my local repository and re-pulled it to ensure that i
> have a clean one before building and the same problem keeps popping
> up.

There is no need to re-pull the repository. The quickest way to clean
out build objects is to use git:

    $ git clean -dqxf

After which, you will have a pristine working directory.

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

Kazuki Sakamoto | 1 Oct 2009 15:17
Picon

Re: MacVim 64/32 bit, Intel, 10.5+ to test


Hi,

On Thu, Oct 1, 2009 at 5:45 AM, björn <bjorn.winckler@...> wrote:
> http://rapidshare.com/files/287063551/MacVim-32_64bit-Leopard-090930.zip

I tried it on Leopard intel and Snow Leopard.

> A sidenote: being built against the 10.5 SDK means that the above
> binary actually doesn't break 'transp' (yay, I guess).

'transp' worked properly on Leopard and Snow Leopard. good!

However, it could not render any multibyte character (wide character)
on Leopard and Snow Leopard.

input multibyte character via im or
loaded file included multibyte character,
after that MacVim doesn't render any chatacter. just empty window.
and puts message.

2009-10-01 21:55:09.892 MacVim[98918:903] NSMutableRLEArray
objectAtIndex:effectiveRange:: Out of bounds

I compiled it myself too, the problem occurred as well.
I'm investigating it using source code, but I have no clue yet...

sakamoto

--~--~---------~--~----~------------~-------~--~----~
(Continue reading)

Kazuki Sakamoto | 1 Oct 2009 15:45
Picon

Re: MacVim 64/32 bit, Intel, 10.5+ to test


For your information,

On Thu, Oct 1, 2009 at 10:17 PM, Kazuki Sakamoto
> However, it could not render any multibyte character (wide character)
> on Leopard and Snow Leopard.

I have compiled it with --with-macarchs="i386" --with-macsdk="10.5"
on Snow Leopard, and I have tested it on Snow Leopard.
It worked correctly for multibyte characters.

It might be related with 64bit for wide(multibyte) characters.

sakamoto

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

björn | 1 Oct 2009 17:24
Picon
Gravatar

Re: MacVim 64/32 bit, Intel, 10.5+ to test


2009/10/1 Kazuki Sakamoto:
>
> I tried it on Leopard intel and Snow Leopard.

So Leopard works.  Excellent!

>> A sidenote: being built against the 10.5 SDK means that the above
>> binary actually doesn't break 'transp' (yay, I guess).
>
> 'transp' worked properly on Leopard and Snow Leopard. good!

The question is: who is going to figure out how to get 'transp' to
work with the 10.6 SDK?  (To everybody who uses 'transp': please help
me figure this out!)

> However, it could not render any multibyte character (wide character)
> on Leopard and Snow Leopard.
>
> input multibyte character via im or
> loaded file included multibyte character,
> after that MacVim doesn't render any chatacter. just empty window.
> and puts message.
>
> 2009-10-01 21:55:09.892 MacVim[98918:903] NSMutableRLEArray
> objectAtIndex:effectiveRange:: Out of bounds
>
> I compiled it myself too, the problem occurred as well.
> I'm investigating it using source code, but I have no clue yet...

(Continue reading)

Adam Mercer | 1 Oct 2009 17:34
Picon
Gravatar

Re: MacVim 64/32 bit, Intel, 10.5+ to test


On Wed, Sep 30, 2009 at 15:45, björn <bjorn.winckler@...> wrote:

> I have a feeling that it won't run on 10.5 because of the Perl version
> it is linked against.  If so, please to an "otool -L
> MacVim.app/Contents/MacOS/*" and tell me which libraries are _not_ on
> your 10.5 system.

Getting the following on my Intel Leopard system:

Dyld Error Message:
  Library not loaded: /System/Library/Perl/lib/5.10/libperl.dylib
  Referenced from: /Users/ram/Desktop/MacVim.app/Contents/MacOS/Vim
  Reason: image not found

This is the only library that my Leopard System doesn't have.

Cheers

Adam

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

björn | 1 Oct 2009 18:20
Picon
Gravatar

Re: MacVim 64/32 bit, Intel, 10.5+ to test


2009/10/1 Adam Mercer:
>
> On Wed, Sep 30, 2009 at 15:45, björn <bjorn.winckler@...> wrote:
>
>> I have a feeling that it won't run on 10.5 because of the Perl version
>> it is linked against.  If so, please to an "otool -L
>> MacVim.app/Contents/MacOS/*" and tell me which libraries are _not_ on
>> your 10.5 system.
>
> Getting the following on my Intel Leopard system:
>
> Dyld Error Message:
>  Library not loaded: /System/Library/Perl/lib/5.10/libperl.dylib
>  Referenced from: /Users/ram/Desktop/MacVim.app/Contents/MacOS/Vim
>  Reason: image not found
>
> This is the only library that my Leopard System doesn't have.

Ok, I guess Sakamoto installed Perl 5.10 manually.  Does Leopard have
Perl 5.8.9 installed by default?  ($ ls /System/Library/Perl)

I will try to fix Perl compilation but it is kind of tricky since Perl
is not a framework (Python and Ruby are) so I a may be forced to
continue building the snapshot without Perl support.

Thanks for trying out the binary,
Björn

--~--~---------~--~----~------------~-------~--~----~
(Continue reading)

Tyson Roberts | 1 Oct 2009 18:30
Picon

Re: encoding

Be sure to do a look at the man page for encoding in vim - it's nowhere near as straight forward as you might expect, and there are some strange special cases you might be running into where one encoding will override others at unexpected times.


On Fri, Oct 2, 2009 at 12:27 AM, björn <bjorn.winckler-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

2009/9/30 Doris Wagner:
>
> hi list,
>
> I am using vim from the terminal (mac os 10.5); I often use german
> umlauts;
>
> now, when I write the umlaut ö with another editor, in my case with
> texshop, and open the file with vim, there ist no ö displayed, but
> <9a>;
> apparently, something with the encoding is wrong;
>
> my .vimrc-settings are as in
>
> http://hoepfl.de/articles/2007/01/vimderbar.html
>
> recommended, that is:
>
> set encoding=utf-8
> set fileencoding=
> setglobal fileencoding=utf-8
> set fileencodings=ucs-bom,utf-8,latin1 set termencoding=latin1
>
>
> so can anyone help me?

Hi Doris,

It seems that texshop is not using UTF-8 so either tell it to use
UTF-8 or set the proper file encoding in Vim.  I don't know which is
the correct one though...maybe somebody else on the list knows, or ask
on vim_use.

Björn




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


Gmane