Can you please provide more info? If i use the below command to compile my 
project, the linker error still pops up.

Just to recap,

My packages A and B statically link a common library LIBA. Also, Package B 
imports A. Compilation of the individual packages is successful but when i 
try to create a binary (using package main which imports B) I get a linker 
error for redefinition of the library.


I understand that Im linking the library twice (once in package A and once 
in B) but I cant compile the individual packages without linking it in each 
of the packages.


package A:

package A
/*
#cgo LDFLAGS: -Bstatic  ${SRCDIR}/../lib/libeventbridge.a
*/
import "C"


The same thing in package B:

package B

import "A"
/*
#cgo LDFLAGS: -Bstatic ${SRCDIR}/../lib/libeventbridge.a
*/
import "C"


Thanks,
Sriram

On Saturday, October 29, 2016 at 7:54:49 PM UTC+5:30, kumargv wrote:
>
> Hi Mate,
>
> why Don't you try to make a static binary 
>
> go build --ldflags ' -extldflags "-static"' filename.go
>
> On Thursday, October 27, 2016 at 8:10:55 PM UTC+5:30, pat.s...@gmail.com 
> wrote:
>>
>> Folks,
>>
>> Two of my packages have dependency on the same C library. I have linked 
>> them successfully using the LDFLAGS directives. 
>>
>> But I'm facing a multiple definitions error when linking my project 
>> executable
>>
>>
>> Here is an overview of my project structure:
>>
>> Pkg A -> depends on LIBA
>>
>> Pkg B (imports Pkg A) -> and also depends on LIBA
>>
>> Pkg Main imports B
>>
>>
>> Commands used to build: In Pkg Main directory: go build
>>
>>
>>
>> Appreciate any thoughts on this issue
>>
>>
>> Thanks!
>>
>

-- 
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 options, visit https://groups.google.com/d/optout.

Reply via email to