You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
I have a project which builds a static library. This library is used as a dependency by other (shared) libraries, and also by a program that must be statically linked. The problem I'm facing is with external dependencies:
The definition above works well when rpm_support is used by a shared library or by a non-static executable; but when used in the statically linked program, the external rpm dependency gets resolved as librpm.so, whereas I need it to be librpm.a. Is there a way to propagate the "static" flag of the user of the dependency to the external dependencies?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I have a project which builds a static library. This library is used as a dependency by other (shared) libraries, and also by a program that must be statically linked. The problem I'm facing is with external dependencies:
The definition above works well when
rpm_support
is used by a shared library or by a non-static executable; but when used in the statically linked program, the externalrpm
dependency gets resolved aslibrpm.so
, whereas I need it to belibrpm.a
. Is there a way to propagate the "static" flag of the user of the dependency to the external dependencies?Something like:
Beta Was this translation helpful? Give feedback.
All reactions