Skip to content
This repository has been archived by the owner on Jul 24, 2023. It is now read-only.

Why not just use pkg-config? #8

Closed
tv42 opened this issue Feb 3, 2014 · 1 comment · Fixed by #10
Closed

Why not just use pkg-config? #8

tv42 opened this issue Feb 3, 2014 · 1 comment · Fixed by #10

Comments

@tv42
Copy link

tv42 commented Feb 3, 2014

Hi. I'm left a bit confused about the installation instructions; why go through all that trouble? It seems to work fine for me after this simple patch:

[0 tv@brute ~/go/src/github.com/sbinet/go-python]$ git diff
diff --git i/python.go w/python.go
index c0b9440..3373cf3 100644
--- i/python.go
+++ w/python.go
@@ -1,6 +1,7 @@
 // simplistic wrapper around the python C-API
 package python

+// #cgo pkg-config: python
 //#include "Python.h"
 //#include <stdlib.h>
 //#include <string.h>
@sbinet
Copy link
Owner

sbinet commented Feb 4, 2014

hi,

yeah... I didn't use pkg-config because the name for the pkg-config isn't standardised at all between distros and OSes (ie: python, python2, python-2, python-27, ... ?)
in retrospect, fiddling with pkg-config naming in a simple cgo_flags.go file is perhaps somewhat easier than with Makefiles :)

I'll push something today along these lines.

-s

sbinet added a commit that referenced this issue Feb 4, 2014
@sbinet sbinet closed this as completed in #10 Feb 4, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants