Re: Information about ffmpeg compile problems on windows

Martin Bayer <[email protected]> Mon, 27 Jun 2005 16:11:25 +0200
Newsgroups gmane.comp.video.gephex.devel
Message-ID <[email protected]>
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0969795024==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig2DF967D275A3EF36544D42CB"

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

> I tried FFMpeg-20050626 now...and it does about the same... (same linker
> warnings, but compiles fine).

The reason for the linker warning could be that we link the static
version of ffmpeg against a dynamic library. You could try to build
shared object library of ffmpeg and link the (frbin and ffmpegout)
modules against that.

Martin

--------------enig2DF967D275A3EF36544D42CB
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)

iD8DBQFCwAkTCm3i57PRsbsRApBDAJ9+vBj+vesHCulPe9uRdHv9BKjP4QCdHuE/
UolM90J6gOG4y5NgRTE0ldw=
=oJ98
-----END PGP SIGNATURE-----

--------------enig2DF967D275A3EF36544D42CB--

--===============0969795024==
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

--===============0969795024==--