Re: [FFmpeg-devel] How to make the link.exe as MSVC's link

2014-12-16 Thread Jesse Jiang
Yes, it is true.
But I think this job is not hard, we can use which command to get the cl path. 
Like $ which cl/c/Program Files (x86)/Microsoft Visual Studio 12.0/VC/BIN/cl.exe
Then we can replace the cl.exe with link.exe, so we can got the correct link 
for msvc.
But the problem is I do not know how to operator the string in configure.
Thanks for anyone can help.

 Date: Tue, 16 Dec 2014 09:57:56 +0100
 From: j...@videolan.org
 To: ffmpeg-devel@ffmpeg.org
 Subject: Re: [FFmpeg-devel] How to make the link.exe as MSVC's link
 
 On 16 Dec, Jesse Jiang wrote :
  I know, but I want make it more easly. It will confusuon the beginer.
 
 Beginners should probably not compile FFmpeg.
 
 -- 
 Jean-Baptiste Kempf
 http://www.jbkempf.com/ - +33 672 704 734
 Sent from my Electronic Device
 ___
 ffmpeg-devel mailing list
 ffmpeg-devel@ffmpeg.org
 http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
  
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


[FFmpeg-devel] How to make the link.exe as MSVC's link

2014-12-15 Thread Jesse Jiang
Hi All,


I want to make MSVC build ffmpeg more easily. There is a problem, if we launch 
msys.bat which in mingw enviroment, the link.exe in msys will conflict with 
link.exe in MSVC.


So I try to change the configure like this


msvc)
# Check whether the current MSVC version needs the C99 converter.
# From MSVC 2013 (compiler major version 18) onwards, it does actually
# support enough of C99 to build ffmpeg. Default to the new
# behaviour if the regexp was unable to match anything, since this
# successfully parses the version number of existing supported
# versions that require the converter (MSVC 2010 and 2012).
cl_major_ver=$(cl 21 | sed -n 's/.*Version 
\([[:digit:]]\{1,\}\)\..*/\1/p')
if [ -z $cl_major_ver ] || [ $cl_major_ver -ge 18 ]; then
cc_default=cl
ld_default=/c/Program Files (x86)/Microsoft Visual Studio 
12.0/VC/BIN/link.exe
else
cc_default=c99wrap cl
ld_default=link
fi


“VC/BIN/link.exe” only be used in X86, if it is x64 or arm, the path is 
different.


But I found that, the cl and link.exe is in the same folder, so is there any 
way to get the cl path, and then modify the path with link’s path.


Thanks all.


Best regards,

Jesse






Sent from Windows Mail
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


Re: [FFmpeg-devel] How to make the link.exe as MSVC's link

2014-12-15 Thread Jesse Jiang
I know, but I want make it more easly. It will confusuon the beginer.






Sent from Surface





From: Derek Buitenhuis
Sent: ‎Tuesday‎, ‎December‎ ‎16‎, ‎2014 ‎12‎:‎06‎ ‎PM
To: FFmpeg development discussions and patches





On 12/16/2014 12:39 AM, Jesse Jiang wrote:
 Hi All,
 
 
 I want to make MSVC build ffmpeg more easily. There is a problem, if we 
 launch msys.bat which in mingw enviroment, the link.exe in msys will conflict 
 with link.exe in MSVC.

This is covered in the documentation:

http://ffmpeg.org/platform.html#Microsoft-Visual-C_002b_002b-or-Intel-C_002b_002b-Compiler-for-Windows

Look under notes.

- Derek
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


[FFmpeg-devel] FFmpeg in Microsoft Media Foudation

2014-12-05 Thread Jesse Jiang
Hi All,




Is there any open-source project which using ffmpeg in MFT(Microsoft Media 
Foundation). I know there is Lav project for DShow. So is there any plant to 
move to MFT.




I want to create an open-source project like this, but I have less experience 
on this. I hope some experts can invoke my project.




Best regards 

Jesse 






Sent from Surface
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


Re: [FFmpeg-devel] WinRT API support patch

2014-11-20 Thread Jesse Jiang
Hi Reimar,
Because of Windows RT cannot use CryptographicBuffer or _beginthreadex API, so 
I try to use rand() instead of it, or we need to write own function instead of 
it. If we use WinRT api to instead of these apis, it will cause more bugs.
Best regards,Jesse
 From: reimar.doeffin...@gmx.de
 Date: Thu, 20 Nov 2014 09:18:30 +0100
 To: ffmpeg-devel@ffmpeg.org
 Subject: Re: [FFmpeg-devel] WinRT API support patch
 
 On 20 November 2014 08:34:54 CET, Jesse Jiang jessejiang0...@outlook.com 
 wrote:
 Add WinRT API supports   
 
 At least 2 fairly major issues:
 1) using rand() basically never is correct. Use the appropriate 
 CryptographicBuffer function (yes, that means you need some C++ code 
 unfortunately).
 2) CreateThread is not compatible with _beginthreadex, there is a good reason 
 why we use this. Using the other without additional changes will cause 
 memleaks or worse. I am not even sure it is at all possible to use 
 CreateThread correctly for us.
 
 ___
 ffmpeg-devel mailing list
 ffmpeg-devel@ffmpeg.org
 http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
  
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


Re: [FFmpeg-devel] WinRT API support patch

2014-11-20 Thread Jesse Jiang
Hi JB,
Based on my understanding, mingw-w64 need gcc, so in this way, we need to 
linked gcc library into our App.  I don't want a big library with our Apps.
I know the mingw is a correct way, but how could it works with MSVC?

 Date: Thu, 20 Nov 2014 09:53:27 +0100
 From: j...@videolan.org
 To: ffmpeg-devel@ffmpeg.org
 Subject: Re: [FFmpeg-devel] WinRT API support patch
 
 On 20 Nov, Jesse Jiang wrote :
  Add WinRT API supports
 
 This patch is wrong on almost every level.
 
 rand() is wrong.
 modifying configure because your headers are broken is wrong too.
 doing an API rewrapper in FFmpeg is the wrong place, look at
 winstorecompat in mingw-w64.
 
 With my kindest regards,
 
 -- 
 Jean-Baptiste Kempf
 http://www.jbkempf.com/ - +33 672 704 734
 Sent from my Electronic Device
 ___
 ffmpeg-devel mailing list
 ffmpeg-devel@ffmpeg.org
 http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
  
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


Re: [FFmpeg-devel] WinRT API support patch

2014-11-20 Thread Jesse Jiang
Do you mean that we can use rand() instead of CryptGenRandom in ffmpeg?

 Date: Thu, 20 Nov 2014 12:17:10 +0100
 From: j...@videolan.org
 To: ffmpeg-devel@ffmpeg.org
 Subject: Re: [FFmpeg-devel] WinRT API support patch
 
 1. libgcc is not big
 2. MSVC 2013 has correctly defined headers to solve the rand issue and 
 the configure part.
 
 Le 20/11/2014 11:34, Jesse Jiang a écrit :
  Hi JB,
  Based on my understanding, mingw-w64 need gcc, so in this way, we need to 
  linked gcc library into our App.  I don't want a big library with our Apps.
  I know the mingw is a correct way, but how could it works with MSVC?
 
  Date: Thu, 20 Nov 2014 09:53:27 +0100
  From: j...@videolan.org
  To: ffmpeg-devel@ffmpeg.org
  Subject: Re: [FFmpeg-devel] WinRT API support patch
 
  On 20 Nov, Jesse Jiang wrote :
  Add WinRT API supports
 
  This patch is wrong on almost every level.
 
  rand() is wrong.
  modifying configure because your headers are broken is wrong too.
  doing an API rewrapper in FFmpeg is the wrong place, look at
  winstorecompat in mingw-w64.
 
  With my kindest regards,
 
  --
  Jean-Baptiste Kempf
  http://www.jbkempf.com/ - +33 672 704 734
  Sent from my Electronic Device
  ___
  ffmpeg-devel mailing list
  ffmpeg-devel@ffmpeg.org
  http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
  
  ___
  ffmpeg-devel mailing list
  ffmpeg-devel@ffmpeg.org
  http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 
 
 
 -- 
 Jean-Baptiste Kempf
 http://www.jbkempf.com/ - +33 672 704 734
 Sent from my Electronic Device
 ___
 ffmpeg-devel mailing list
 ffmpeg-devel@ffmpeg.org
 http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
  
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


Re: [FFmpeg-devel] WinRT API support patch

2014-11-20 Thread Jesse Jiang
Hi All,
I did some research, rand() is pseudo random. CryptGenRandom is the system-wide 
seed, but it cannot be used in Windows RT.
I try to use CryptographicBuffer, which is Windows RT API, but there is a 
problem. This API needs to link Windows.winmd. The Windows.winmd just like a 
DLL, but it may different from Windows RT and Windows Phone. First, the SDKs 
are in the different PATH,Second, the files are also different.
It means that developer need to choice platform first, and then compiler for 
different library.
I hope ffmpeg only depends on support win32 apis and CRT apis.
So is there any way to instead of srand(time(0)); rand(); ? How about c++11 
random or Mersenne twister Algorithmic
Best regards,Jesse
Date: Fri, 21 Nov 2014 02:49:59 +0100
From: michae...@gmx.at
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] WinRT API support patch

On Fri, Nov 21, 2014 at 01:43:29AM +, Jesse Jiang wrote:
 Do you mean that we can use rand() instead of CryptGenRandom in ffmpeg?
 
rand() is completely wrong
its not even doing the correct operation
 
rand() is pseudo random
the code requires a strong (and non pseudo) random value
 
[...]
-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
 
When you are offended at any man's fault, turn to yourself and study your
own failings. Then you will forget your anger. -- Epictetus

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel 
  
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


Re: [FFmpeg-devel] WinRT API support patch

2014-11-20 Thread Jesse Jiang
Now, I find a function get_generic_seed()
So, I use this function will work fine?

uint32_t av_get_random_seed(void){uint32_t seed;
#if HAVE_CRYPTGENRANDOMHCRYPTPROV provider;if 
(CryptAcquireContext(provider, NULL, NULL, PROV_RSA_FULL,  
  CRYPT_VERIFYCONTEXT | CRYPT_SILENT)) {BOOL ret = 
CryptGenRandom(provider, sizeof(seed), (PBYTE) seed);
CryptReleaseContext(provider, 0);if (ret)return seed;
}#endif
#if HAVE_WINRTAPIreturn get_generic_seed();#endif
if (read_random(seed, /dev/urandom) == sizeof(seed))return seed; 
   if (read_random(seed, /dev/random)  == sizeof(seed))return seed;  
  return get_generic_seed();}
 From: jessejiang0...@outlook.com
 To: ffmpeg-devel@ffmpeg.org
 Date: Fri, 21 Nov 2014 03:51:12 +
 Subject: Re: [FFmpeg-devel] WinRT API support patch
 
 Hi All,
 I did some research, rand() is pseudo random. CryptGenRandom is the 
 system-wide seed, but it cannot be used in Windows RT.
 I try to use CryptographicBuffer, which is Windows RT API, but there is a 
 problem. This API needs to link Windows.winmd. The Windows.winmd just like a 
 DLL, but it may different from Windows RT and Windows Phone. First, the SDKs 
 are in the different PATH,Second, the files are also different.
 It means that developer need to choice platform first, and then compiler for 
 different library.
 I hope ffmpeg only depends on support win32 apis and CRT apis.
 So is there any way to instead of srand(time(0)); rand(); ? How about c++11 
 random or Mersenne twister Algorithmic
 Best regards,Jesse
 Date: Fri, 21 Nov 2014 02:49:59 +0100
 From: michae...@gmx.at
 To: ffmpeg-devel@ffmpeg.org
 Subject: Re: [FFmpeg-devel] WinRT API support patch
 
 On Fri, Nov 21, 2014 at 01:43:29AM +, Jesse Jiang wrote:
  Do you mean that we can use rand() instead of CryptGenRandom in ffmpeg?
  
 rand() is completely wrong
 its not even doing the correct operation
  
 rand() is pseudo random
 the code requires a strong (and non pseudo) random value
  
 [...]
 -- 
 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
  
 When you are offended at any man's fault, turn to yourself and study your
 own failings. Then you will forget your anger. -- Epictetus
 
 ___
 ffmpeg-devel mailing list
 ffmpeg-devel@ffmpeg.org
 http://ffmpeg.org/mailman/listinfo/ffmpeg-devel   
   
 ___
 ffmpeg-devel mailing list
 ffmpeg-devel@ffmpeg.org
 http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
  
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


[FFmpeg-devel] WinRT API support patch

2014-11-19 Thread Jesse Jiang
Add WinRT API supports

0001-Add-WindowsRT-support.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


[FFmpeg-devel] Fix restrict bug

2014-11-19 Thread Jesse Jiang
*restrict has been replaced by av_restrict. I meet this bug when I compiler for 
ARM in VS. There should be some other places need to be replaced.
Best regards,Jesse

0002-restrict-bug-should-be-replaced-by-av_restrict.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


[FFmpeg-devel] Move ffmpeg to WinRT

2014-11-17 Thread Jesse Jiang
Hi All,
I want to move ffmpeg to WinRT platform, like Windows Store and Windows Phone. 
As the GCC cannot compiler to ARM-COFF, so I convert the GNU-style assembly 
codes to ARM-style codes. Also the codes are open-sourced, here 
https://github.com/qyljcy/FFmpeg
Now this project can be compiled, but I didn't know if the assembly codes work 
well.
I want to know, if there is any test project to test the function like 
ff_ps_add_squares_neon, ect. As the WinRT platform is different from win32 or 
linux, so I need to test them one by one.
I hope someone can help me, or work together.
Thanks very much
Best regards,Jesse
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


Re: [FFmpeg-devel] Move ffmpeg to WinRT

2014-11-17 Thread Jesse Jiang
This project should be used as static library. 
I have done two things in this project. One is converting unsupported APIs to 
Winrt API, other is converting arm assembly codes to support armasm which VS 
compiler.
Don't worry about Windows 10. Windows 10 is based on the WinRT API, maybe there 
are some differences, but most of them are the same.
 From: bumblebritche...@gmail.com
 Date: Mon, 17 Nov 2014 05:37:11 -0500
 To: ffmpeg-devel@ffmpeg.org
 Subject: Re: [FFmpeg-devel] Move ffmpeg to WinRT
 
 As of Windows 10, WinRT is deprecated, so it's kind of a waste of time dude
 :/
 
 On Mon, Nov 17, 2014 at 5:02 AM, Jesse Jiang jessejiang0...@outlook.com
 wrote:
 
  Hi All,
  I want to move ffmpeg to WinRT platform, like Windows Store and Windows
  Phone. As the GCC cannot compiler to ARM-COFF, so I convert the GNU-style
  assembly codes to ARM-style codes. Also the codes are open-sourced, here
  https://github.com/qyljcy/FFmpeg
  Now this project can be compiled, but I didn't know if the assembly codes
  work well.
  I want to know, if there is any test project to test the function like
  ff_ps_add_squares_neon, ect. As the WinRT platform is different from win32
  or linux, so I need to test them one by one.
  I hope someone can help me, or work together.
  Thanks very much
  Best regards,Jesse
  ___
  ffmpeg-devel mailing list
  ffmpeg-devel@ffmpeg.org
  http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 
 ___
 ffmpeg-devel mailing list
 ffmpeg-devel@ffmpeg.org
 http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
  
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


Re: [FFmpeg-devel] Move ffmpeg to WinRT

2014-11-17 Thread Jesse Jiang
Hi JB,
Haven't seen you for a long time. I have sent you email before to talk about 
the GCC compile for ARM-COFF.
At that time, I know it is hard for GCC to do this, so I try to convert the 
assembly codes. If there is gas-preproc, it should be a better choice. 
Where can I find this script, is it open-source?
Best regards,Jesse

 Date: Mon, 17 Nov 2014 12:32:55 +0100
 From: j...@videolan.org
 To: ffmpeg-devel@ffmpeg.org
 Subject: Re: [FFmpeg-devel] Move ffmpeg to WinRT
 
 On 17 Nov, Jesse Jiang wrote :
  I want to move ffmpeg to WinRT platform, like Windows Store and Windows 
  Phone. As the GCC cannot compiler to ARM-COFF, so I convert the GNU-style 
  assembly codes to ARM-style codes. Also the codes are open-sourced, here 
  https://github.com/qyljcy/FFmpeg
  Now this project can be compiled, but I didn't know if the assembly codes 
  work well.
 
 This work is useless...
 
 FFmpeg can already be compiled on WinRT, with gas-preproc...
 
 -- 
 Jean-Baptiste Kempf
 http://www.jbkempf.com/ - +33 672 704 734
 Sent from my Electronic Device
 ___
 ffmpeg-devel mailing list
 ffmpeg-devel@ffmpeg.org
 http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
  
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


Re: [FFmpeg-devel] Move ffmpeg to WinRT

2014-11-17 Thread Jesse Jiang
Thanks Micheal 
Date: Tue, 18 Nov 2014 04:56:56 +0100
From: michae...@gmx.at
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Move ffmpeg to WinRT

On Tue, Nov 18, 2014 at 03:07:34AM +, Jesse Jiang wrote:
 Hi JB,
 Haven't seen you for a long time. I have sent you email before to talk about 
 the GCC compile for ARM-COFF.
 At that time, I know it is hard for GCC to do this, so I try to convert the 
 assembly codes. If there is gas-preproc, it should be a better choice. 
 Where can I find this script, is it open-source?
 
yes it is
 
our variant of it is here:
https://github.com/FFmpeg/gas-preprocessor
 
[...]
-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
 
No human being will ever know the Truth, for even if they happen to say it
by chance, they would not even known they had done so. -- Xenophanes

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel 
  
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel