Re: Information about ffmpeg compile problems on windows

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0248208616==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigE937E9CC2BD4BA7E601AEA27"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigE937E9CC2BD4BA7E601AEA27
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


> Since it is not difficult and does not obfuscate the code too much to
> support both the old and the new API I vote for supporting both.
> Gives us much more flexibility in choosing an ffmpeg version if problems
> occur (as already happened in the past).

ok

Martin


--------------enigE937E9CC2BD4BA7E601AEA27
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCv//ECm3i57PRsbsRAqrlAKCHZ63UUDvqXVMO6qe465IZ371MoQCePG7D
UuFSceW9b5rOfxp6KeuOLEs=
=YI7N
-----END PGP SIGNATURE-----

--------------enigE937E9CC2BD4BA7E601AEA27--

--===============0248208616==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
gephex-devel mailing list
[email protected]
http://lists.gephex.org/mailman/listinfo/gephex-devel

--===============0248208616==--