Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CMake doesn't appear to be using pkg-config where available for FreeBSD #508

Open
bevanweiss opened this issue Sep 28, 2020 · 0 comments · May be fixed by #509
Open

CMake doesn't appear to be using pkg-config where available for FreeBSD #508

bevanweiss opened this issue Sep 28, 2020 · 0 comments · May be fixed by #509

Comments

@bevanweiss
Copy link

This is the problem when you have such a good program with GitAhead... I want to run it everywhere.
Trying to build for FreeBSD, and have run into two problems, both due to the location of headers / libraries really.

  1. FreeBSD doesn't have inotify out of the box, so it requires libinotify to provide the bridge to kqueue for this. Having installed libinotify with pkg, it appears that "/usr/local/include" isn't being included in the CXXFLAGs.

  2. If I provide CXX_FLAGS to CMake this works, and it compiles, however it now doesn't link since it wants libinotify (-L/usr/local/lib -linotify) passed in on the linker flags. Passing LDFLAGS to CMake did not appear to work here however.

I think it would be amazing if on BSD derivatives if pkg-config could be used to pick up the libinotify locations.
And I think a similar situation occurs with libssh2 (on the linker flags).

Maybe it's just my FreeBSD (FuryBSD) environment that is wacky.
Either way, I'll have a look at it, since I am very keen on getting GitAhead working in this environment :)

Thanks for a great application

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 a pull request may close this issue.

1 participant