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
55a6d8d9
Commit
55a6d8d9
authored
Dec 22, 2011
by
Michael Niedermayer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
libpostproc: increase LIBPOSTPROC_VERSION_MICRO to 100
Signed-off-by:
Michael Niedermayer
<
michaelni@gmx.at
>
parent
d5874e9c
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
3 additions
and
1 deletion
+3
-1
postprocess.c
libpostproc/postprocess.c
+2
-0
postprocess.h
libpostproc/postprocess.h
+1
-1
No files found.
libpostproc/postprocess.c
View file @
55a6d8d9
...
...
@@ -75,6 +75,7 @@ try to unroll inner for(x=0 ... loop to avoid these damn if(x ... checks
#include "config.h"
#include "libavutil/avutil.h"
#include "libavutil/avassert.h"
#include <inttypes.h>
#include <stdio.h>
#include <stdlib.h>
...
...
@@ -90,6 +91,7 @@ try to unroll inner for(x=0 ... loop to avoid these damn if(x ... checks
unsigned
postproc_version
(
void
)
{
av_assert0
(
LIBPOSTPROC_VERSION_MICRO
>=
100
);
return
LIBPOSTPROC_VERSION_INT
;
}
...
...
libpostproc/postprocess.h
View file @
55a6d8d9
...
...
@@ -31,7 +31,7 @@
#define LIBPOSTPROC_VERSION_MAJOR 51
#define LIBPOSTPROC_VERSION_MINOR 2
#define LIBPOSTPROC_VERSION_MICRO
0
#define LIBPOSTPROC_VERSION_MICRO
10
0
#define LIBPOSTPROC_VERSION_INT AV_VERSION_INT(LIBPOSTPROC_VERSION_MAJOR, \
LIBPOSTPROC_VERSION_MINOR, \
...
...
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