|
meta-go dependencies
#dunfell
#golang
You can ask Konrad about it. But please keep the mailing list in CC, so that the entire conversation remains visible and archived to all. Alex
You can ask Konrad about it. But please keep the mailing list in CC, so that the entire conversation remains visible and archived to all. Alex
|
By
Alexander Kanavin
· #58044
·
|
|
meta-go dependencies
#dunfell
#golang
Right, I don't think such a dedicated layer exists. You may want to go over the list of dependencies and type them into http://layers.openembedded.org/layerindex/branch/master/recipes/ to see if anyth
Right, I don't think such a dedicated layer exists. You may want to go over the list of dependencies and type them into http://layers.openembedded.org/layerindex/branch/master/recipes/ to see if anyth
|
By
Alexander Kanavin
· #58043
·
|
|
meta-go dependencies
#dunfell
#golang
Hello Sure thanks it is https://github.com/aler9/rtsp-simple-server Ed Watson
Hello Sure thanks it is https://github.com/aler9/rtsp-simple-server Ed Watson
|
By
Ed Watson
· #58041
·
|
|
meta-go dependencies
#dunfell
#golang
It helps if you can name the project. Are the sources public? Alex
It helps if you can name the project. Are the sources public? Alex
|
By
Alexander Kanavin
· #58040
·
|
|
meta-go dependencies
#dunfell
#golang
Hello, I am trying to include a go project in my yocto build. It has quite a few dependencies. I may have missed something, there is a meta-go around that I have missed? Or a quick way of pulling in m
Hello, I am trying to include a go project in my yocto build. It has quite a few dependencies. I may have missed something, there is a meta-go around that I have missed? Or a quick way of pulling in m
|
By
Ed Watson
· #58039
·
|
|
#golang Build tools required during go generate
#golang
I tweaked the recipe a bit (you should use SRCREV, versus a tag), etc, and added some link flags to make things static. This tends to be why I write my own do_compile for go applications, so I can use
I tweaked the recipe a bit (you should use SRCREV, versus a tag), etc, and added some link flags to make things static. This tends to be why I write my own do_compile for go applications, so I can use
|
By
Bruce Ashfield
· #55263
·
|
|
#golang Build tools required during go generate
#golang
Sure here you go: ``` SUMMARY = "easyjson" DESCRIPTION = "easy json command util" HOMEPAGE = "https://github.com/mailru/easyjson" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://src/${GO_IMPORT}/LICENSE;md
Sure here you go: ``` SUMMARY = "easyjson" DESCRIPTION = "easy json command util" HOMEPAGE = "https://github.com/mailru/easyjson" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://src/${GO_IMPORT}/LICENSE;md
|
By
Sebastian Rühl
· #55262
·
|
|
#golang Build tools required during go generate
#golang
It varies based on the application, the ones I've dealt with, tend to have a -static flag. Of course, the flag may not be exposed, and in those scenarios, I patch the Makefile/build. If you have publi
It varies based on the application, the ones I've dealt with, tend to have a -static flag. Of course, the flag may not be exposed, and in those scenarios, I patch the Makefile/build. If you have publi
|
By
Bruce Ashfield
· #55258
·
|
|
#golang Build tools required during go generate
#golang
Yep might be… For me that’s desirable as these a built-utils, it’s golang and I see no benefit in having them dynamically linked anyay. Any tips how to statically link these? As far as I understand th
Yep might be… For me that’s desirable as these a built-utils, it’s golang and I see no benefit in having them dynamically linked anyay. Any tips how to statically link these? As far as I understand th
|
By
Sebastian Rühl
· #55257
·
|
|
#golang Build tools required during go generate
#golang
I'd bet it is a variant of this: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14386 Bruce
I'd bet it is a variant of this: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14386 Bruce
|
By
Bruce Ashfield
· #55256
·
|
|
#golang Build tools required during go generate
#golang
Here some outputs: Bitbake -c devshell target-recipe sh-4.4# easyjson Segmentation fault sh-4.4# strace easyjson execve("/workdir/build/tmp/work/aarch64-fslc-linux/datadog-agent/7.31.1-r0/recipe-sysro
Here some outputs: Bitbake -c devshell target-recipe sh-4.4# easyjson Segmentation fault sh-4.4# strace easyjson execve("/workdir/build/tmp/work/aarch64-fslc-linux/datadog-agent/7.31.1-r0/recipe-sysro
|
By
Sebastian Rühl
· #55255
·
|
|
WG: [yocto] #golang Build tools required during go generate
#golang
There is literaly no stacktrace just a segmentation fault pretty early in the execution (like 3rd instruction or something). I will send more outputs as soon as my dual-core has finished compiling stu
There is literaly no stacktrace just a segmentation fault pretty early in the execution (like 3rd instruction or something). I will send more outputs as soon as my dual-core has finished compiling stu
|
By
Sebastian Rühl
· #55254
·
|
|
#golang Build tools required during go generate
#golang
do you have stack trace ? that might give some more info on whats going on
do you have stack trace ? that might give some more info on whats going on
|
By
Khem Raj
· #55252
·
|
|
#golang Build tools required during go generate
#golang
Hi yoto-devs/users, in order to get a golang application to run which relies on `go generate` calls I wrote special recipes for this tools and include them in my original recipe. However I always get
Hi yoto-devs/users, in order to get a golang application to run which relies on `go generate` calls I wrote special recipes for this tools and include them in my original recipe. However I always get
|
By
Sebastian Rühl
· #55250
·
|
|
SSH_AUTH_SOCK unavailable when pulling modules
#golang
Adding BB_ORIGENV to do_compile[vardepsexclude] solved the issue. Thanks for your help!
Adding BB_ORIGENV to do_compile[vardepsexclude] solved the issue. Thanks for your help!
|
By
Sven
· #53406
·
|
|
SSH_AUTH_SOCK unavailable when pulling modules
#golang
Hi Richard, Unfortunately, that doesn't make the error messages go away. I agree that it's not great that go-mod fetches during do_compile but that's the way it currently is. For completeness sake, he
Hi Richard, Unfortunately, that doesn't make the error messages go away. I agree that it's not great that go-mod fetches during do_compile but that's the way it currently is. For completeness sake, he
|
By
Sven
· #53405
·
|
|
SSH_AUTH_SOCK unavailable when pulling modules
#golang
On Mon, 2021-05-03 at 11:25 -0700, Sven via lists.yoctoproject.org wrote: Hi, I have put together a recipe inheriting from go-mod. This project depends on > out-of-repo modules that sit in private rep
On Mon, 2021-05-03 at 11:25 -0700, Sven via lists.yoctoproject.org wrote: Hi, I have put together a recipe inheriting from go-mod. This project depends on > out-of-repo modules that sit in private rep
|
By
Richard Purdie
· #53399
·
|
|
SSH_AUTH_SOCK unavailable when pulling modules
#golang
Hi Sven, No, I do not use any custom go-based recipe. BR, Quentin
Hi Sven, No, I do not use any custom go-based recipe. BR, Quentin
|
By
Quentin Schulz
· #53395
·
|
|
SSH_AUTH_SOCK unavailable when pulling modules
#golang
Hi Quentin, Thanks for your reply. Did you have success with this technique when compiling a go-mod recipe where some of the go dependencies sit in private repos? The standard git fetcher works for me
Hi Quentin, Thanks for your reply. Did you have success with this technique when compiling a go-mod recipe where some of the go dependencies sit in private repos? The standard git fetcher works for me
|
By
Sven
· #53394
·
|
|
SSH_AUTH_SOCK unavailable when pulling modules
#golang
On Ubuntu, when the password for my SSH key is in the gnome keyring, I run: eval $(/usr/bin/gnome-keyring-daemon --start --components=pkcs11,secrets,ssh); export SSH_AUTH_SOCK in the terminal that wil
On Ubuntu, when the password for my SSH key is in the gnome keyring, I run: eval $(/usr/bin/gnome-keyring-daemon --start --components=pkcs11,secrets,ssh); export SSH_AUTH_SOCK in the terminal that wil
|
By
Quentin Schulz
· #53354
·
|