Re: Go toolchain in SDK


Srini
 

Unlike other languages go has the ability to produce cross platform binaries. In my case, I just used my go to produce binaries for my yocto based target and just included it. it was too much effort to incorporate the go toolchain. But then it was > 1 year ago.

srini


From: yocto@... <yocto@...> on behalf of Khem Raj via lists.yoctoproject.org <raj.khem=gmail.com@...>
Sent: Thursday, June 18, 2020 8:27 PM
To: Robert Berger <robert.berger.yocto.user@...>; yocto@... <yocto@...>
Cc: Robert Berger <robert.berger@...>
Subject: Re: [yocto] Go toolchain in SDK
 


On 6/16/20 1:55 PM, Robert Berger wrote:
> Hi,
>
> What is the "proper" way to add the Go toolchain to an SDK nowadays
> (dunfell)?
>

I dont think there is sample image target for image based SDKs

> I saw there is in poky:
>
> ./meta/recipes-core/meta/meta-go-toolchain.bb
>
> but I am not quite sure how to build an SDK with meta-go-toolchain
> included.

that is more like a meta-toolchain target

>
> so I added something like that to local.conf which seems to work for the
> "classic" SDK:
>
> # --> golang stuff
> # attempt to add golang to SDK
> TOOLCHAIN_HOST_TASK_append = " \
>     packagegroup-go-cross-canadian-${MACHINE} \
> "
>
> TOOLCHAIN_TARGET_TASK_append = " \
>     ${@multilib_pkg_extend(d, 'packagegroup-go-sdk-target')} \
> "
> # <-- golang stuff
>
> bitbake core-image-sato-sdk -c populate_sdk
>
> and currently also for:
> bitbake core-image-sato-sdk -c populate_sdk_ext
>
> I don't think that's the way it was intended.
>
> Can you please enlighten me?

what you did is roughly what should be needed. Maybe you might want
to create a -dev image

perhaps adding nativesdk-go to TOOLCHAIN_HOST_TASK might get everything
you need

>
> Regards,
>
> Robert
>
>
>



Join {yocto@lists.yoctoproject.org to automatically receive all group messages.