| 1 |
On Thu, Jul 23, 2015 at 12:37:59AM +0200, Manuel Rüger wrote: |
| 2 |
> On 23.07.2015 00:19, William Hubbs wrote: |
| 3 |
> > All, |
| 4 |
> > |
| 5 |
> > after some testing, i decided that the eclass should make both the |
| 6 |
> > golibdir and the prefixed version of it available with functions. |
| 7 |
> > |
| 8 |
> > The reason for this is that the prefixed golibdir should be part of |
| 9 |
> > GOPATH when building packages. |
| 10 |
> > |
| 11 |
> > The functions are get_golibdir and get_golibdir_gopath. |
| 12 |
> > |
| 13 |
> > Here's the updated patch. |
| 14 |
> > |
| 15 |
> > William |
| 16 |
> > |
| 17 |
> |
| 18 |
> Have you tested this with FEATURES="multilib-strict"? |
| 19 |
> |
| 20 |
> I guess you need $(get_libdir) from multilib eclass to set the correct |
| 21 |
> libpath. |
| 22 |
> |
| 23 |
> Manuel |
| 24 |
> |
| 25 |
> |
| 26 |
|
| 27 |
No, because Go has its own way of separating architecture/os specific |
| 28 |
packages. /usr/lib/go is the standard Go library and /usr/lib/go-gentoo |
| 29 |
will hold third party Go packages. Under them, there are src directories |
| 30 |
and directories named ${GOOS}_${GOARCH} which store the packages for the |
| 31 |
specific OS/ARCH. |
| 32 |
|
| 33 |
William |
Archives