1 |
|
INSTALL |
2 |
|
======= |
3 |
|
|
4 |
Table of contents: |
Table of contents: |
5 |
================== |
================== |
6 |
|
|
115 |
# cd ${xvidcore}/build/generic |
# cd ${xvidcore}/build/generic |
116 |
# ./configure --host=i386-mingw32 --build=i386-pc-linux-gnu |
# ./configure --host=i386-mingw32 --build=i386-pc-linux-gnu |
117 |
|
|
118 |
And then build as usual. You can build the vfw frontend as well, |
And then build as usual. |
119 |
specifying the CC compiler and the WINDRES tool to use on the make |
|
120 |
command line. |
As the example uses the Win32 target, we can even build the vfw frontend. |
121 |
|
Additional requirements are: |
122 |
|
- Resource compiler (the Makefile uses the syntax of windres from the |
123 |
|
GNU CC suite, but you can easily modify the cmd line) |
124 |
|
- GNU make (other make programs may have problem with shell expansion) |
125 |
|
|
126 |
|
So to cross compile the VFW frontend, you just need to override the |
127 |
|
Makefile variables pointing to the compiler and the resource compiler. |
128 |
|
These variables are CC and WINDRES. |
129 |
# cd ${xvidcore}/vfw/bin |
# cd ${xvidcore}/vfw/bin |
130 |
# make -f Makefile.cygwin CC=i386-mingw32-gcc WINDRES=i386-mingw32-windres |
# make CC=i386-mingw32-gcc WINDRES=i386-mingw32-windres |
131 |
|
|
132 |
|
|
133 |
1.e/ What is the meaning of xvidcore Makefile output. |
1.e/ What is the meaning of xvidcore Makefile output. |
149 |
Installing 'file' in 'a/dir' |
Installing 'file' in 'a/dir' |
150 |
- L: file |
- L: file |
151 |
Linking 'file' |
Linking 'file' |
152 |
|
- W: file |
153 |
|
Compiling the Win32 resource 'file' |
154 |
|
|
155 |
|
|
156 |
1.f/ Building a Debian package. |
1.f/ Building a Debian package. |
205 |
You have first to retrieve the sources from the xvid CVS repository |
You have first to retrieve the sources from the xvid CVS repository |
206 |
using a tool like WinCVS. Then follow the normal steps explained in |
using a tool like WinCVS. Then follow the normal steps explained in |
207 |
the previous section. |
the previous section. |
208 |
|
|
209 |
|
NB: your CVS program may not convert text files to the cr/lf windows |
210 |
|
text. In that case opening project files in MSVC will result in |
211 |
|
some weird error messages from MSVC. To fix that, you have to |
212 |
|
convert all .dsp files to the cr/lf format. You can do that |
213 |
|
opening the .dsp file in WordPad and saving it. It should now be |
214 |
|
in cr/lf format. |
215 |
|
|
216 |
|
Last edited: $Date: 2003-11-15 01:53:22 $ |