Skip to content

Don't check for Security.framework when cross-compiling#5189

Closed
def- wants to merge 1 commit intocurl:masterfrom
def-:pr-security-framework
Closed

Don't check for Security.framework when cross-compiling#5189
def- wants to merge 1 commit intocurl:masterfrom
def-:pr-security-framework

Conversation

@def-
Copy link
Copy Markdown
Contributor

@def- def- commented Apr 6, 2020

Since it probably won't exist.

@bagder bagder added the build label Apr 6, 2020
@bagder
Copy link
Copy Markdown
Member

bagder commented Apr 6, 2020

Isn't the reason rather that it checks for the local file and not for the cross-compiled version so the check is wrong?

@def-
Copy link
Copy Markdown
Contributor Author

def- commented Apr 6, 2020

Correct. Is there a better way to check?

@bagder
Copy link
Copy Markdown
Member

bagder commented Apr 6, 2020

I have no idea, @nickzman, do you know of if that can be done better?

My comment was more in regards to the commit message here, as reading the patch it seems correct but I found the explanation a little off.

Since it checks for the local file, not the cross-compiled one.
@def- def- force-pushed the pr-security-framework branch from c47500c to 52a86da Compare April 6, 2020 12:59
@def-
Copy link
Copy Markdown
Contributor Author

def- commented Apr 6, 2020

Fixed the commit message.

@bagder bagder closed this in 2ebc123 Apr 6, 2020
@bagder
Copy link
Copy Markdown
Member

bagder commented Apr 6, 2020

Thanks!

@def- def- deleted the pr-security-framework branch April 6, 2020 13:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

2 participants