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
52561d01
Commit
52561d01
authored
Aug 09, 2012
by
Diego Biurrun
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: Drop obsolete shared libs cflags hint to workaround Cygwin gcc bugs
parent
90f7e617
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
15 deletions
+0
-15
platform.texi
doc/platform.texi
+0
-15
No files found.
doc/platform.texi
View file @
52561d01
...
@@ -292,21 +292,6 @@ In order to run FATE you will also need the following "Utils" packages:
...
@@ -292,21 +292,6 @@ In order to run FATE you will also need the following "Utils" packages:
bc, diffutils
bc, diffutils
@end example
@end example
Then run
@example
.
/
configure
@end example
to make a static build.
To build shared libraries add a special compiler flag to work around current
@code
{
gcc
4
-
core
}
package bugs in addition to the normal configure flags:
@example
.
/
configure
--
enable
-
shared
--
disable
-
static
--
extra
-
cflags
=-
fno
-
reorder
-
functions
@end example
If you want to build Libav with additional libraries, download Cygwin
If you want to build Libav with additional libraries, download Cygwin
"Devel" packages for Ogg and Vorbis from any Cygwin packages repository:
"Devel" packages for Ogg and Vorbis from any Cygwin packages repository:
@example
@example
...
...
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