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
f2a7236d
Commit
f2a7236d
authored
Oct 19, 2012
by
Derek Buitenhuis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc/platform: Move a caveat down to the notes section
Signed-off-by:
Derek Buitenhuis
<
derek.buitenhuis@gmail.com
>
parent
ebe46b80
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
5 deletions
+6
-5
platform.texi
doc/platform.texi
+6
-5
No files found.
doc/platform.texi
View file @
f2a7236d
...
...
@@ -120,11 +120,6 @@ you want to run @uref{fate.html, FATE}.
To set up a proper MSVC environment in MSYS, you simply need to run
@code
{
msys.bat
}
from the Visual Studio command prompt.
Caveat: Run @code
{
which link
}
to see which link you are using. If it is located
at @code
{
/
bin
/
link.exe
}
, then you have the wrong link in your @code
{
PATH
}
.
Either move
/
remove that copy, or make sure MSVC's link.exe is higher up in your
@code
{
PATH
}
than coreutils'.
Place @code
{
c
99
wrap.exe
}
, @code
{
c
99
conv.exe
}
, and @code
{
yasm.exe
}
somewhere
in your @code
{
PATH
}
.
...
...
@@ -146,6 +141,12 @@ Notes:
@itemize
@item It is possible that coreutils' @code
{
link.exe
}
conflicts with MSVC's linker.
You can find out by running @code
{
which link
}
to see which @code
{
link.exe
}
you
are using. If it is located at @code
{
/
bin
/
link.exe
}
, then you have the wrong one
in your @code
{
PATH
}
. Either move or remove that copy, or make sure MSVC's
@code
{
link.exe
}
takes precedence in your @code
{
PATH
}
over coreutils'.
@item If you wish to build with zlib support, you will have to grab a compatible
zlib binary from somewhere, with an MSVC import lib, or if you wish to link
statically, you can follow the instructions below to build a compatible
...
...
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