Skip to content

Conversation

@saper
Copy link
Collaborator

@saper saper commented Feb 26, 2017

On BSDs headers will be in /usr/local/include which
is not added to the include path automatically.

Follow-up-to: #1195

@saper
Copy link
Collaborator Author

saper commented Feb 26, 2017

Maybe this would even work for Windows?

@implausible
Copy link
Member

The only reason to bring libcurl into NodeGit is to enable proxy and authenticated proxy transports in OSX and Linux. Windows already has full support for proxies.

@implausible
Copy link
Member

@saper should rebase this on master so the 32 bit linux tests passes. This is definitely a good idea.

@johnhaley81
Copy link
Collaborator

@saper could you rebase this please? I'd like to get this in for the next release. Thanks!

On BSDs headers will be in /usr/local/include which
is not added to the include path automatically.
@saper
Copy link
Collaborator Author

saper commented Feb 28, 2017

Rebased... well it was master and the time I wrote this :) and there were no conflicts

@rsmarples
Copy link
Contributor

What needs to be done here to progress this?
I need these changes for building nodegit on NetBSD.

@valpackett
Copy link

Please merge this, npm i nodegit fails on FreeBSD without this, having to locally fix this and npm link is getting annoying.

@mfechner
Copy link

Are there plans to include this patch, I can confirm that it fixed the problem.

sgilroy pushed a commit to TwineHealth/nodegit that referenced this pull request Feb 25, 2018
On BSDs headers will be in /usr/local/include which
is not added to the include path automatically.

(cherry picked from commit 785f184)
[nodegit#1237]
@antoinell
Copy link

antoinell commented Jul 3, 2018

The code in this pull request helps with the build on FreeBSD and Ubuntu 16.04. Hopefully it can get merged soon. I see that there is an error in a build on windows done by appveyor, this seems unrelated to the code changes here which do not affect windows as far as I understand.

@Croydon
Copy link
Contributor

Croydon commented Sep 25, 2018

@implausible Can we merge this now? Both #1545 and #1519 is containing it too, but getting this done step by step seems reasonable.

@implausible
Copy link
Member

@Croydon The tests are failing. @saper Any chance you can rebase this to get the tests running again on CI? It looks like Travis doesn't even know about this PR.

Otherwise if @saper is unavailable, I would support it if you, @Croydon, took control of this PR by opening a new branch + PR with it. We would close this PR, reference this PR in your PR, and merge your PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants