Re: [go-nuts] output files from build of swig file

Thanks for confirming, I realised this by digging into the go build code. // Run SWIG on one SWIG input file. 3553 func (b *builder) swigOne(p *Package, file, obj string, pcCFLAGS []string, cxx bool, intgosize string) (outGo, outC string, err error) { 3554 cgoCPPFLAGS, cgoCFLAGS,

Re: [go-nuts] output files from build of swig file

On Mon, Oct 17, 2016 at 4:11 AM, wrote: > > I have a follow-up question, how can I instrument my go code so that I can > set the include path that is used to resolve '%include' statements in my > swig code. Currently I have relative paths in my swig file, and I would

Re: [go-nuts] output files from build of swig file

Thanks for confirming my suspicions. I have a follow-up question, how can I instrument my go code so that I can set the include path that is used to resolve '%include' statements in my swig code. Currently I have relative paths in my swig file, and I would like to put '/usr/include' on the

Re: [go-nuts] output files from build of swig file

On Fri, Oct 14, 2016 at 3:42 AM, wrote: > > Im trying to build a swig wrapper to a c library using go build. I know the > swig interface file is good as it builds correctly with the swig command and > generated the expected go wrapper file and the wrapper c file. I know