Skip to content

Conversation

@aylen384
Copy link

@aylen384 aylen384 commented Jul 3, 2019

No description provided.

@WardCunningham
Copy link
Owner

Is there some advantage to being dynamically linked?

I see the industry moving away from this as just another opportunity to fail. See golang, for example.

@WardCunningham
Copy link
Owner

Blame traces the choice of static back to: #3

@aylen384
Copy link
Author

aylen384 commented Jul 3, 2019

For languages like go and d this may be true but for c/c++ it actually has been the opposite in the last years. Static binaries are are less and less well supported.
Most distributions don't even package the .a files for most of their libraries so you can't even build on that distros.

But if you are concerned about static building, it might make sence to add a second target m-static that will drop out a static binary.
Providing prebuilt binaries for download from your website might be the only real usecase for static binaries.

@aylen384
Copy link
Author

aylen384 commented Jul 3, 2019

Go and D will actually build dynamically linked binaries that only link against glibc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants