Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
FFmpeg
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
libremedia
Tethys
FFmpeg
Commits
f2a7236d
Commit
f2a7236d
authored
12 years ago
by
Derek Buitenhuis
Browse files
Options
Downloads
Patches
Plain Diff
doc/platform: Move a caveat down to the notes section
Signed-off-by:
Derek Buitenhuis
<
derek.buitenhuis@gmail.com
>
parent
ebe46b80
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/platform.texi
+6
-5
6 additions, 5 deletions
doc/platform.texi
with
6 additions
and
5 deletions
doc/platform.texi
+
6
−
5
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
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment