-
-
Notifications
You must be signed in to change notification settings - Fork 684
/
INSTALLx.txt
156 lines (117 loc) · 4.93 KB
/
INSTALLx.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
INSTALLx.txt - cross-compiling Vim on Unix
Content:
1. Introduction
2. Necessary arguments for "configure"
3. Necessary environment variables for "configure"
4. Example
1. INTRODUCTION
===============
This document discusses cross-compiling VIM on Unix-like systems. We assume
you are already familiar with cross-compiling and have a working cross-compile
environment with at least the following components:
* a cross-compiler
* a libc to link against
* ncurses library to link against
Discussing how to set up a cross-compile environment would go beyond the scope
of this document. See http://www.kegel.com/crosstool/ for more information and
a script that aids in setting up such an environment.
The problem is that "configure" needs to compile and run small test programs
to check for certain features. Running these test programs can't be done when
cross-compiling so we need to pass the results these checks would produce via
environment variables. See the list of variables and the examples at the end of
this document.
2. NECESSARY ARGUMENTS FOR "configure"
======================================
You need to set the following "configure" command line switches:
--build=... :
The build system (i.e. the platform name of the system you compile on
right now).
For example, "i586-linux".
--host=... :
The system on which VIM will be run. Quite often this the name of your
cross-compiler without the "-gcc".
For example, "powerpc-603-linux-gnu".
--target=... :
Only relevant for compiling compilers. Set this to the same value as
--host.
--with-tlib=... :
Which terminal library to use.
For example, "ncurses".
3. NECESSARY ENVIRONMENT VARIABLES FOR "configure"
==================================================
Additionally to the variables listed here you might want to set the CPPFLAGS
environment variable to enable optimization for your target system (e.g.
"CPPFLAGS=-march=arm5te").
The following variables need to be set:
ac_cv_sizeof_int:
The size of an "int" C type in bytes. Should be "4" on all 32bit
machines.
vi_cv_path_python_conf:
If Python support is enabled, set this variable to the path for
Python's library implementation. This is a path like
"/usr/lib/pythonX.Y/config" (the directory contains a file
"config.c").
vi_cv_path_python_epfx:
If Python support is enabled, set this variable to the execution
prefix of your Python interpreter (that is, where it thinks it is
running).
This is the output of the following Python script:
import sys; print sys.exec_prefix
vi_cv_path_python_pfx:
If Python support is enabled, set this variable to the prefix of your
Python interpreter (that is, where it was installed).
This is the output of the following Python script:
import sys; print sys.prefix
vi_cv_var_python_version:
If Python support is enabled, set this variable to the version of the
Python interpreter that will be used.
This is the output of the following Python script:
import sys; print sys.version[:3]
vim_cv_bcopy_handles_overlap:
Whether the "bcopy" C library call is able to copy overlapping
memory regions. Set to "yes" if it does or "no" if it does not.
You only need to set this if vim_cv_memmove_handles_overlap is set
to "no".
vim_cv_getcwd_broken:
Whether the "getcwd" C library call is broken. Set to "yes" if you
know that "getcwd" is implemented as 'system("sh -c pwd")', set to
"no" otherwise.
vim_cv_memcpy_handles_overlap:
Whether the "memcpy" C library call is able to copy overlapping
memory regions. Set to "yes" if it does or "no" if it does not.
You only need to set this if both vim_cv_memmove_handles_overlap
and vim_cv_bcopy_handles_overlap are set to "no".
vim_cv_memmove_handles_overlap:
Whether the "memmove" C library call is able to copy overlapping
memory regions. Set to "yes" if it does or "no" if it does not.
vim_cv_stat_ignores_slash:
Whether the "stat" C library call ignores trailing slashes in the path
name. Set to "yes" if it ignores them or "no" if it does not ignore
them.
vim_cv_tgetent:
Whether the "tgetent" terminal library call returns a zero or non-zero
value when it encounters an unknown terminal. Set to either the string
"zero" or "non-zero", corresponding.
vim_cv_terminfo:
Whether the environment has terminfo support. Set to "yes" if so,
otherwise set to "no".
vim_cv_toupper_broken:
Whether the "toupper" C library function works correctly. Set to "yes"
if you know it's broken, otherwise set to "no".
4. EXAMPLE:
===========
Assuming the target system string is "armeb-xscale-linux-gnu" (a Intel XScale
system) with glibc and ncurses, the call to configure would look like this:
ac_cv_sizeof_int=4 \
vim_cv_getcwd_broken=no \
vim_cv_memmove_handles_overlap=yes \
vim_cv_stat_ignores_slash=yes \
vim_cv_tgetent=zero \
vim_cv_terminfo=yes \
vim_cv_toupper_broken=no \
./configure \
--build=i586-linux \
--host=armeb-xscale-linux-gnu \
--target=armeb-xscale-linux-gnu \
--with-tlib=ncurses
Written 2007 by Marc Haisenko <marc@darkdust.net> for the VIM project.