Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

2016-10-19 23:56 GMT+02:00 Josh Sloat : >>Where did he say that? > > OP discusses failed methods here: > https://www.mail-archive.com/ffmpeg-user@ffmpeg.org/msg11151.html (Now an important part of my email is missing above) I don't think he discusses a suggested method

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

>Where did he say that? OP discusses failed methods here: https://www.mail-archive.com/ffmpeg-user@ffmpeg.org/msg11151.html >Please fix your quoting I’m using the Reply button in mail.app and the “>" symbol for quoting. Pretty standard stuff. Not sure what more I can do. > On Oct 19, 2016,

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

2016-10-19 23:28 GMT+02:00 joshsloat : >>Could it also be a matter of reading the mails I write? > > I’ve read every single line of every single post in this thread. > You gave the original poster a solution and he said it didn’t work. Where did he say that? Please fix

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

>Could it also be a matter of reading the mails I write? I’ve read every single line of every single post in this thread. You gave the original poster a solution and he said it didn’t work. I can either repeat what the OP did and end up with the same result - or we can move things closer to

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

2016-10-18 19:21 GMT+02:00 Josh Sloat : > We’re not currently compiling ffmpeg from source. Sorry, your mail is difficult to read: To which of my questions is this the answer? Carl Eugen ___ ffmpeg-user mailing list

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

Thanks Moritz and Phil. You are precisely correct as to why I posted the question where I did. >how about learning to use your mail client? Good grief, Reindl. Comments like these are precisely why every conversation on the Internet devolves into a flame war. No help, no value, just

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

> however, if you have a precompiled binary from somewhere then bother the > person who built it Or, you could discuss it here, where there might be some other people who've used it. P ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

Am 19.10.2016 um 01:24 schrieb Josh Sloat: How is this helpful? how about learning to use your mail client? that starts with not top-posting and create your own topic by compose a new mail and *not* reply to something else - however, if you have a precompiled binary from somewhere then

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

How is this helpful? > On Oct 18, 2016, at 7:23 PM, Reindl Harald wrote: > > > > Am 19.10.2016 um 01:11 schrieb joshsloat: >> I didn’t create the subject line. I was responding to an existing thread > > oh my > ___ >

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

Am 19.10.2016 um 01:11 schrieb joshsloat: I didn’t create the subject line. I was responding to an existing thread oh my ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

I didn’t create the subject line. I was responding to an existing thread. The original poster started with a downloaded binary (just like me) and got rejected (just like me). The original question had to do with trying to find a way to compile from source that would get around the rejection.

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

Am 18.10.2016 um 19:21 schrieb Josh Sloat: We’re not currently compiling ffmpeg from source. We’re using the binary obtained directly from: http://www.ffmpegmac.net so WHAT is the point of a subject containing "compiling" then?

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

Anand mentioned that compiling with that option also resulted in rejection: >I tried to build myself using this ./configure >--disable-protocol=tls_securetransport. They rejected it. The conversation seemed to sputter out after that, so I am reaching out for clarity. We’re not currently

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

2016-10-18 17:53 GMT+02:00 joshsloat : > Carl - It looks like there was some unaddressed confusion > about why this is resulting in rejection. Why do you think so? What's wrong with --disable-securetransport? And where can I find the source code of your FFmpeg distribution?

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

ok let me be clear with my Question Whether --enable-static will embed the libraries? or just link them? When i move the created ffmpeg to another machine i fails to load the dyld. -- View this message in context:

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

Am 18.09.2016 um 00:49 schrieb Kieran O Leary: Hi On 17 Sep 2016 11:42 p.m., "Carl Eugen Hoyos" wrote: Unrelated: Am I the only one who has serious trouble receiving Phil's emails? Yes, on Gmail they go straight to spam, and are only included in a thread when someone

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

Hi On 17 Sep 2016 11:42 p.m., "Carl Eugen Hoyos" wrote: > > > > Unrelated: Am I the only one who has serious trouble receiving > Phil's emails? > Yes, on Gmail they go straight to spam, and are only included in a thread when someone replies.

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

On 9/18/16, Carl Eugen Hoyos wrote: > 2016-09-17 21:12 GMT+02:00 Phil Rhodes : >>> We are not Apple. >> >> Well, no, but someone on the list might have experience of doing this. >> In fact, I know for a fact that someone on the list has experience

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

2016-09-17 2:54 GMT+02:00 muruganandh : > Apple is rejecting whatever i do. > > 1. I tried to use the static ffmpeg (3.1.3) by tessus. They rejected it. I would expect that this build includes SecureTransport (which is useful), we already know (thanks to you) that this is

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

On Fri, Sep 16, 2016 at 17:54:38 -0700, muruganandh wrote: > Apple is rejecting whatever i do. [...] > 3. I have no idea how to build ffmpeg so that Apple guys accept it. Does Apple not provide any reason for rejection? Moritz ___ ffmpeg-user mailing

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

> We are not Apple. Well, no, but someone on the list might have experience of doing this. In fact, I know for a fact that someone on the list has experience of doing this. So why not let the conversation continue? P ___ ffmpeg-user mailing list

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

On 9/17/16, muruganandh wrote: > Apple is rejecting whatever i do. > > 1. I tried to use the static ffmpeg (3.1.3) by tessus. They rejected it. > 2. I tried to build myself using this ./configure > --disable-protocol=tls_securetransport. They rejected it. > 3. I have no idea

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

Where are you providing the source code of your app? I am trying to submit the app to mac app store. Should i post it somewhere and link it here? -- View this message in context: http://ffmpeg-users.933282.n4.nabble.com/Compiling-FFmpeg-without-SecIdentityCreate-API-tp4676487p4677598.html

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

Apple is rejecting whatever i do. 1. I tried to use the static ffmpeg (3.1.3) by tessus. They rejected it. 2. I tried to build myself using this ./configure --disable-protocol=tls_securetransport. They rejected it. 3. I have no idea how to build ffmpeg so that Apple guys accept it. -- View

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

2016-09-16 13:13 GMT+02:00 muruganandh : > This is the configure command i am using > > ./configure --enable-libx264 --disable-securetransport This configure line is supposed to fail so you cannot use it. Carl Eugen ___

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

Thanks so much Carl. --disable-securetransport worked perfectly. But i see a new issue: dyld: Library not loaded: /usr/local/opt/x264/lib/libx264.148.dylib This is the configure command i am using ./configure --enable-libx264 --disable-securetransport I think the x264 is just linked NOT

Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

Anand gmail.com> writes: > I need to compile & create FFmpeg executable without (or > altering name) this method "SecIdentityCreate" because it > seems it conflicts from the framework > '/System/Library/Frameworks/Security.framework/Versions/A/Security' How can I reproduce this compilation

[FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API

Hi, I need to compile & create FFmpeg executable without (or altering name) this method "SecIdentityCreate" because it seems it conflicts from the framework '/System/Library/Frameworks/Security.framework/Versions/A/Security' Does anybosy know how to do that? Thanks Anand