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

buildsystem: no transitive linkage for internally used libraries #1115

Merged
merged 1 commit into from
May 29, 2019

Conversation

TheJJ
Copy link
Member

@TheJJ TheJJ commented May 27, 2019

if the linking is declared PUBLIC, e.g. all the python modules that
link against libopenage would link to all of libopenage's dependencies
again. when one of those, e.g. libnyan.so, is updated, the module will be
linked again. this means if e.g. libnyan is updated, all python modules
are relinked. this commit removes this transitive linking, and python
modules won't be rebuilt any more.

@TheJJ TheJJ added improvement Enhancement of an existing component area: buildsystem Related to our cmake/python buildsystem labels May 27, 2019
if the linking is declared PUBLIC, e.g. all the python modules that
link against libopenage would link to all of libopenage's dependencies
again. when one of those, e.g. libnyan.so, is updated, the module will be
linked again. this means if e.g. libnyan is updated, all python modules
are relinked. this commit removes this transitive linking, and python
modules won't be rebuilt any more.
@TheJJ TheJJ force-pushed the private-library-linkage branch from 47239a7 to bce3575 Compare May 29, 2019 13:11
@TheJJ TheJJ merged commit 855d1ef into SFTtech:master May 29, 2019
@TheJJ TheJJ deleted the private-library-linkage branch May 29, 2019 13:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: buildsystem Related to our cmake/python buildsystem improvement Enhancement of an existing component
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant