awesome go install is working :) thanks so much!
On Monday, June 26, 2017 at 12:06:17 AM UTC-7, Ian Lance Taylor wrote:
>
> On Sun, Jun 25, 2017 at 9:34 PM, >
> wrote:
> > Thanks, my gcc and g++ versions were indeed different. I've set them
> both to
> > 4.8 now and the -no-pie error has gone
On Sun, Jun 25, 2017 at 9:34 PM, wrote:
> Thanks, my gcc and g++ versions were indeed different. I've set them both to
> 4.8 now and the -no-pie error has gone away.
>
> I'm seeing warnings from "go build" command regarding syntax in the c++
> library - if they are just warnings, would go install
Thanks, my gcc and g++ versions were indeed different. I've set them both
to 4.8 now and the -no-pie error has gone away.
I'm seeing warnings from "go build" command regarding syntax in the c++
library - if they are just warnings, would go install continue with placing
output files in the $GOBI
On Fri, Jun 23, 2017 at 2:52 PM, wrote:
> go version go1.7.4 linux/amd64
>
>
> The link you're referring to is an issue with the LANG env variable; mine is
> set to LANG=en_US.UTF-8 which the OP mentioned go build succeeds with
Is it possible that you are using a different version of gcc and g++
go version go1.7.4 linux/amd64
The link you're referring to is an issue with the LANG env variable; mine
is set to LANG=en_US.UTF-8 which the OP mentioned go build succeeds with
On Friday, June 23, 2017 at 2:43:11 PM UTC-7, Ian Lance Taylor wrote:
>
> On Fri, Jun 23, 2017 at 2:09 PM, >
> wr
On Fri, Jun 23, 2017 at 2:09 PM, wrote:
>
> Hi, I'm trying to wrap a c++ library with swig to be called by Go.
>
> I've gotten "go build" to run up to the point to where I get the error:
> g++-4.8: error: unrecognized command line option '-no-pie'
>
> The library I'm using is only supported up to
On Fri, Jun 23, 2017 at 11:27 AM, wrote:
>
> I'm using go version 1.7.4 on linux/amd64 and trying to run go build on a
> .swigcxx file. I also have a .go file that has the package name and string:
> import "C"
> package mdm
>
>
> import "C"
>
>
>
> My .swigcxx file is trying to include a library
Don't forget the linker flags ...
#cgo LDFLAGS: -L -l
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more option
Got past that error now :) was missing a space between multiple -I
On Friday, June 23, 2017 at 2:08:59 PM UTC-7, Sebastien Binet wrote:
>
>
>
> On Fri, Jun 23, 2017 at 10:53 PM, >
> wrote:
>
>> Thanks. My .go file contains just the following:
>>
>> package mypackage
>> // #cgo CXXFLAGS: -I/usr/fo
On Fri, Jun 23, 2017 at 10:53 PM, wrote:
> Thanks. My .go file contains just the following:
>
> package mypackage
> // #cgo CXXFLAGS: -I/usr/folder/subfolder
> import "C"
>
> and when I do "go build" or "go build -x" I get an error that the #include
> library i'm using is not found. has anyone ru
Thanks. My .go file contains just the following:
package mypackage
// #cgo CXXFLAGS: -I/usr/folder/subfolder
import "C"
and when I do "go build" or "go build -x" I get an error that the #include
library i'm using is not found. has anyone run into this before?
On Friday, June 23, 2017 at 1:39:2
On Fri, Jun 23, 2017 at 10:28 PM, wrote:
> Could someone elaborate how the CXXFLAGS will look in the .go file?
>
> Is it like
> // #cgo CXXFLAGS: -I/
>
>
>
yes.
more precisely:
// #cgo CXXFLAGS: -I/path/to/some/folder
import "C"
with no blank like between the comment with the preprocessor-like
Could someone elaborate how the CXXFLAGS will look in the .go file?
Is it like
// #cgo CXXFLAGS: -I/
On Thursday, April 13, 2017 at 4:35:54 PM UTC-7, larry104 wrote:
>
>
>>
>> CXXFLAGS
>>
>> See https://golang.org/cmd/cgo .
>>
>> Ian
>>
>
> Cool - that works now like a charm - so much simpl
>
>
>
> CXXFLAGS
>
> See https://golang.org/cmd/cgo .
>
> Ian
>
Cool - that works now like a charm - so much simpler than before - no more
100 line long complicated make file.
Thanks a lot for your help!!!
--
You received this message because you are subscribed to the Google Groups
"golang
On Thu, Apr 13, 2017 at 11:40 AM, larry104 wrote:
>>
>>
>> The go tool will run whichever one is first on your PATH.
>>
>> Ian
>
>
> My mistake - there was a typo - Tracing what go build does with the -x
> option shows that swig run correct now (interface file with .swigcxx
> extension). Then it s
>
>
>
> The go tool will run whichever one is first on your PATH.
>
> Ian
>
My mistake - there was a typo - Tracing what go build does with the -x
option shows that swig run correct now (interface file with .swigcxx
extension). Then it seems cg0 compiles all files in the _obj file with gcc4
On Wed, Apr 12, 2017 at 5:51 PM, larry104 wrote:
> I added a .go file - now go build complains about the incorrect swig version
> - The system installed swig version is 3.0.2 but I have 3.0.12 installed in
> linked in my bin. How can I tell go build to use this version instead?
The go tool will
I added a .go file - now go build complains about the incorrect swig
version - The system installed swig version is 3.0.2 but I have 3.0.12
installed in linked in my bin. How can I tell go build to use this version
instead?
--
You received this message because you are subscribed to the Google
The .go file can just be a dummy file with no real purpose?
On Wednesday, April 12, 2017 at 5:06:35 PM UTC-7, Ian Lance Taylor wrote:
>
> On Wed, Apr 12, 2017 at 4:42 PM, larry104 > wrote:
> >
> > I seems I need to manually run swig (swig -go -cgo -c++ -intgosize 64
> > mylib.i) - it does not
On Wed, Apr 12, 2017 at 4:42 PM, larry104 wrote:
>
> I seems I need to manually run swig (swig -go -cgo -c++ -intgosize 64
> mylib.i) - it does not seem that 'go build' picks up the .i or .swig file.
> Then I need to call 'go tool cgo mylib.go'. This creates an _obj directory
> with a bunch of fil
For c++, your swig file needs to have a swigcxx extension for the go tool
to run swig properly.
On Apr 12, 2017 4:42 PM, "larry104" wrote:
I seems I need to manually run swig (swig -go -cgo -c++ -intgosize 64
mylib.i) - it does not seem that 'go build' picks up the .i or .swig file.
Then I need
I seems I need to manually run swig (swig -go -cgo -c++ -intgosize 64
mylib.i) - it does not seem that 'go build' picks up the .i or .swig file.
Then I need to call 'go tool cgo mylib.go'. This creates an _obj directory
with a bunch of files. After that I tried calling 'go build'. This errors
o
On Tue, Apr 11, 2017 at 5:00 PM, larry104 wrote:
>
> As it seems with go 1.5 there is no 6c compiler anymore - I had it all
> working with go 1.4 but now upgrading to 1.8.1 I'm lost. Does anyone know a
> link to an example how the flow from c++ to an .so library which I can
> include as package i
23 matches
Mail list logo
