Skip to content
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

cmd/go: 'go build' with swig deletes shared libraries needed to run output #7155

Closed
gopherbot opened this issue Jan 20, 2014 · 3 comments
Closed
Milestone

Comments

@gopherbot
Copy link

by tschroed:

As discussed in https://groups.google.com/d/topic/golang-nuts/xRjXJ2RfIHk/discussion,
when building code with swig dependencies, the emitted shared library is discarded if go
is run in build mode rather than install.

This means that it's not possible to test the executable before releasing it into the
pkg path.

A more useful option would be to land the DSO in the same directory as the executable
target and leave users to specify an appropriate ld.so search path.

Alternatively, statically linking in the swig deps would obviate the problem.

The attached code trivially demonstrates the issue.

Attachments:

  1. goswig.tar.gz (458 bytes)
@ianlancetaylor
Copy link
Contributor

Comment 1:

Labels changed: added release-go1.3maybe, repo-main.

Owner changed to @ianlancetaylor.

Status changed to Accepted.

@gopherbot
Copy link
Author

Comment 3:

CL https://golang.org/cl/97120046 mentions this issue.

@ianlancetaylor
Copy link
Contributor

Comment 4:

This issue was closed by revision 02cc45a.

Status changed to Fixed.

@rsc rsc added this to the Go1.3 milestone Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 25, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants