Philip Prindeville wrote:
> Tony Mechelynck wrote:
>> Philip Prindeville wrote:
>>
>>> Tony Mechelynck wrote:
>>>
>>>> Philip Prindeville wrote:
>>>>
>>>>
>>>>> Sorry for the newbie question, but I'm trying to get Vim (7.1) to port
>>>>> to Astlinux (0.5).
>>>>>
>>>>> Unfortunately, the src/auto/configure file seems to suggest (around line
>>>>> 2801) that cross-compiling isn't supported.
>>>>>
>>>>> Is there a work-around to getting Vim cross-compiled?
>>>>>
>>>>> I was a little surprised: I would have thought that when bringing up a
>>>>> new machine, a lot of people would make Vim part of their early
>>>>> bootstrapping process and get it into the new environment quickly...
>>>>>
>>>>> Thanks,
>>>>>
>>>>> -Philip
>>>>>
>>>>> P.S. Yes, I actually did the read FAQ first, and didn't see anything on
>>>>> cross-compilation...
>>>>>
>>>>>
>>>> If you have a C/C++ compiler and linker (such as gcc) on your astlinux
>>>> box, or
>>>> if there is some known source from which you can get it, then you don't
>>>> need a
>>>> cross-compiler. Just download the sources on the target machine and
>>>> compile
>>>> there. See also my HowTo page
>>>> http://users.skynet.be/antoine.mechelynck/vim/compunix.htm about compiling
>>>> Vim
>>>> on Unix-like systems.
>>>>
>>>>
>>>> Best regards,
>>>> Tony.
>>>>
>>>>
>>> It *is* a Unix box, but it's a run-from-flash system, and compiling on
>>> the system (because the processors typically aren't very fast) is slow
>>> and tedious... plus all the writing of temp files is hard on the flash
>>> media.
>>>
>>> Short answer: much quicker to compile on the host system.
>>>
>>> So... there is no easy way to cross-compile then? The host platform is
>>> Linux Fedora Core 7...
>>>
>>> -Philip
>>>
>> If the existing configure script and top-level Makefile aren't what you
>> want,
>> maybe you can construct a "special-purpose" makefile, maybe src/Make_ast.mak
>> or something? It wouldn't be the first case: after all, compiling on Cygwin
>> for use on native-Windows (using src/Make_cyg.mak) can also be considered a
>> "cross-compile".
>>
>>
>> Best regards,
>> Tony.
>>
>
> 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.
>
> -Philip
I don't know; but the various makefiles in the src/ subdirectory (other than
src/Makefile) bypass configure completely: when using them (e.g. to compile
Vim using various Windows compilers), configure is not used at all. If you
create a new (let's say) src/Make_ast.mak, you could do the same, using Make
variables (which can be set by environment variables) for any "user-settable"
options (such as, e.g., the tiny/small/normal/big/huge featureset, console Vim
or gvim, do or don't include MzScheme/Perl/Python/Ruby/Tcl interfaces and
where are their libraries, etc.). See the various src/Make_*.mak for examples,
and in particular Make_cyg.mak which runs on Windows but in a Unix-like
environment, and cross-compiles a Vim for native-Windows.
Best regards,
Tony.
--
First Law of Procrastination:
Procrastination shortens the job and places the responsibility
for its termination on someone else (i.e., the authority who imposed
the deadline).
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
