On Wednesday 12 December 2007, Ben Schmidt wrote:
>
> > Well, I'm a little confused... the configure that was distributed seems
> > to very deliberately go out of its way to defeat cross-compilation, as
> > opposed to simply being unaware of it (agnostic).
> >
> > I was wondering if there were historical reasons for that.
>
> Possibly. Or maybe it's just the way autoconf works--it has
cross-compilation
> options available by default, so if you don't support them, it may be
smartest to
> make a point of not supporting them. I don't think the way Vim uses
configure is
> quite standard, either, so that may have something to do with it.
>
> I'm sure there's no good reason Vim couldn't be cross compiled. It would
take
> considerable effort, though. But then cross-compilation almost always does!
>
> Ben.
Well, VIM cross-compiles quite nicely, haven't had an issues yet (I'm
cross-compiling to x86, PowerPC and ARM5). I've posted a patch a while ago to
fix configure.in.
The patch includes a README.
Marc
--
Marc Haisenko
Comdasys AG
Rüdesheimer Str. 7
80686 München
Germany
Tel.: +49 (0)89 548 433 321
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
