-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
write build_go_mac.sh file to set up go package so it can be installed more seamlessly #79
Conversation
# to run you need to let the linker know where the linked library files are: | ||
# LD_LIBRARY_PATH="${LD_LIBRARY_PATH:-}:./iroh/ffi" \ | ||
# CGO_LDFLAGS="-liroh -L ./iroh/ffi" \ | ||
# go <actual go command to build or run> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this stay here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, unfortunately from my linux experimentation, it won't recognize the linked files, no matter where I put libiroh.so
. Either the box I was using was ignoring it, or maybe something was wrong with how it was set up for dynamic linking, but I couldn't get it to recognize the cgo flag. I needed to still add the LD_LIBRARY_PATH manually. So until that's confirmed to work I want to leave these instructions in.
linux machines still don't want to recognize
cgo LDFLAG
, but this brings us one step closer and cleaner to getting a golang setting to be smoother.Updates the README for how to build the golang bindings for each platform.