mirror of
https://gitee.com/openharmony/third_party_ffmpeg
synced 2024-11-23 19:30:05 +00:00
Elaborate on the Visual C-- situation.
Originally committed as revision 4716 to svn://svn.ffmpeg.org/ffmpeg/trunk
This commit is contained in:
parent
5f2a42ba35
commit
5062c60c18
@ -200,10 +200,17 @@ the compilation failure then you are probably not qualified for this.
|
||||
|
||||
@section Visual C++ produces many errors.
|
||||
|
||||
You need a C compiler (Visual C++ is not compliant to the C standard).
|
||||
Visual C++ is not compliant to the C standard and does not support
|
||||
the inline assembly used in FFmpeg.
|
||||
If you wish - for whatever weird reason - to use Visual C++ for your
|
||||
project then you can link the Visual C++ code with libav* as long as
|
||||
you compile the latter with a working C compiler. For more information, see
|
||||
the @emph{Visual C++ compatibility} section in the FFmpeg documentation.
|
||||
|
||||
There have been efforts to make FFmpeg compatible with Visual C++ in the
|
||||
past. However, they have all been rejected as too intrusive, especially
|
||||
since MinGW does the job perfectly adequately. None of the core developers
|
||||
work with Visual C++ and thus this item is low priority. Should you find
|
||||
the silver bullet that solves this problem, feel free to shoot it at us.
|
||||
|
||||
@bye
|
||||
|
Loading…
Reference in New Issue
Block a user