Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in / Register
Toggle navigation
F
ffmpeg.wasm-core
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Linshizhi
ffmpeg.wasm-core
Commits
b0ce601c
Commit
b0ce601c
authored
Jun 23, 2013
by
Derek Buitenhuis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc/platform: Add info about ICL
Signed-off-by:
Derek Buitenhuis
<
derek.buitenhuis@gmail.com
>
parent
e21307a2
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
19 additions
and
9 deletions
+19
-9
platform.texi
doc/platform.texi
+19
-9
No files found.
doc/platform.texi
View file @
b0ce601c
...
...
@@ -101,10 +101,10 @@ you can build all libraries as DLLs.
@end itemize
@section Microsoft Visual C
++
@section Microsoft Visual C
++
or Intel C
++
Compiler for Windows
Libav can be built with MSVC using a C
99
-
to
-
C
89
conversion utility and
wrapper.
Libav can be built with MSVC
or ICL
using a C
99
-
to
-
C
89
conversion utility and
wrapper.
For ICL, only the wrapper is used, since ICL supports C
99
.
You will need the following prerequisites:
...
...
@@ -117,28 +117,33 @@ You will need the following prerequisites:
you want to run @uref
{
fate.html, FATE
}
.
@end itemize
To set up a proper
MSVC environment in MSYS, you simply need to run
@code
{
msys.bat
}
from the Visual Studio
command prompt.
To set up a proper
environment in MSYS, you need to run @code
{
msys.bat
}
from
the Visual Studio or Intel Compiler
command prompt.
Place @code
{
makedef
}
, @code
{
c
99
wrap.exe
}
, @code
{
c
99
conv.exe
}
, and @code
{
yasm.exe
}
somewhere in your @code
{
PATH
}
.
Next, make sure @code
{
inttypes.h
}
and any other headers and libs you want to use
are located in a spot that
MSVC can see. Do so by modifying the @code
{
LIB
}
and
@code
{
INCLUDE
}
environment variables to include the @strong
{
Windows
}
paths to
are located in a spot that
the compiler can see. Do so by modifying the @code
{
LIB
}
and
@code
{
INCLUDE
}
environment variables to include the @strong
{
Windows
}
paths to
these directories. Alternatively, you can try and use the
@code
{
--
extra
-
cflags
}
/
@code
{
--
extra
-
ldflags
}
configure options.
Finally, run:
@example
For MSVC:
.
/
configure
--
toolchain
=
msvc
For ICL:
.
/
configure
--
toolchain
=
icl
make
make install
@end example
If you wish to compile shared libraries, add @code
{
--
enable
-
shared
}
to your
configure options. Note that due to the way MSVC
handles
DLL imports and
configure options. Note that due to the way MSVC
and ICL handle
DLL imports and
exports, you cannot compile static and shared libraries at the same time, and
enabling shared libraries will automatically disable the static ones.
...
...
@@ -168,7 +173,12 @@ erroneously included when building Libav.
can see.
@end enumerate
@item Libav has been tested with Visual Studio
2010
and
2012
, Pro and Express.
@item Libav has been tested with the following on i
686
and x
86
_
64
:
@itemize
@item Visual Studio
2010
Pro and Express
@item Visual Studio
2012
Pro and Express
@item Intel Composer XE
2013
@end itemize
Anything else is not officially supported.
@end itemize
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment