[xine-devel] Win32 port [was Re: ffmpeg]

[Frantisek D. <va...@us...>]

(CCing to xine-devel, there are no documentation about it yet and maybe
someone will have good comments)

Hi Michail,
Hi xine hackers,


V =C4=8Ct, 29. 04. 2004 v 19:55, Michail Mametov p=C3=AD=C5=A1e:
> Hello, Frantisek,
>=20
> =20
>=20
> =20
>=20
> On the site sourceforge.net in the mailing list I have read some
> messages about the compilation xine for Windows
> (http://sourceforge.net/mailarchive/message.php?msg_id=3D6837001). I
> have got some problems with compilation ffmpeg for Windows. I would be
> glad for answers to my questions:
>=20

Nice you interested in Windows build.

This was my first work on building xine under Windows. I used MinGW for
ffmpeg and MSVC for other parts of xine. Note however, it's very crazy,
and also MSVC can't handle assembler code in xine. So this hybrid build
is deprecated (but I try keep it updated). If you have problems with
building standalone ffmpeg with MinGW, you should report it to ffmpeg
guys.

So you won't need does this hybrid build, xine should be compilable with
CygWin (you'll need directX headers for video and audio output, freely
downloadable from M$ site). Better MinGW is still in progress (many
fight with autoconf/automake :-)).

> =20
>=20
> 1.       Was this compilation made only in Cygwin or only in Mingw?
>=20
> Or was Cygwin used as a compilator and library Mingw?
>=20
> There are some problems during the loading of dll which uses Cygwin
> out of the program made with MSVC. How were these problems solved?
>=20


> 2.       Was the whole xine compiled or only ffmpeg? If the last one
> was compiled only is it necessary to compile using Cygwin/Mingw
> xine-engine and xine-utils?
>=20

To the hybrid build: xine and all modules with MSVC, ffmpeg in MinGW.
There are required some additional steps to setup MinGW - set PATH to
lib.exe, part of MSVC compiler. ffmpeg will link also .lib files usable
in MSVC for builing ffmpeg xine module.

> 3.       I would be very glad to get make files which were used during
> the compilation for Windows. Or what changes are necessary to be
> brought in them
>=20

Most of things I already commit to xine. If you just build and try xine,
I recommend you using CygWin (then delete OSS audio plugin and build
manually xineui in win32/sources).

If you need build your application in MSVC and use xine-lib, it's
complicated for now. My unfinished patch for MinGW is on this page:
http://xine.czechian.net/win32. While engine (library xine) should be
compiled fine with this patch, some modules can't compile. However I
don't solve yet how to build .lib files for MSVC...

> 4.       What drawbacks are there in functioning of such a build?
>=20
> =20

See above.

There are still some bugs in Win32 version, most visible are sound
output, crashing, problems with nonseekable inputs... See
http://xine.czechian.net/win32.

>=20
> =20
>=20
>    Mikhail,
>=20
>    mi...@mi...
>=20


Cheers,
  Frantisek

PS: I have no time to work on it now, but the part of mentioned MinGW
patch I plan to public on xine-devel and commit soon.