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

Option to only build static libs for components and SCR #318

Open
adammoody opened this issue May 1, 2021 · 3 comments
Open

Option to only build static libs for components and SCR #318

adammoody opened this issue May 1, 2021 · 3 comments
Assignees

Comments

@adammoody
Copy link
Contributor

Some would like to force the build to only build static libs for all components and SCR, so that they force their app to link with static libs. In this case, they are fine with having each library in its own .a, but they just want to disable the .so libs from being built. They are testing ideas now, but I wanted to document those here so I don't forget.

For CMake builds, they pointed to our use of SHARED in ADD_LIBRARY. If we drop SHARED, then cmake will build shared libs depending on its BUILD_SHARED_LIBS=ON/OFF setting.

For lwgrp and dtcmp, we may need to conditionally add a configure flag like --enabled-shared=no.

@adammoody adammoody added this to To do in v3.0rc2 May 1, 2021
@adammoody
Copy link
Contributor Author

Related LLNL/scr-top#12

@adammoody
Copy link
Contributor Author

It was discovered that the tests and/or examples don't build on a static-only build. As a work around, there are options coming to disable building the tests and examples.

However, we need to figure out how to get those to build in case someone really needs them to build in static-only builds.

@adammoody adammoody moved this from To do to Done in v3.0rc2 May 22, 2021
@adammoody adammoody moved this from Done to In progress in v3.0rc2 Jun 2, 2021
@adammoody adammoody self-assigned this Jun 9, 2021
@adammoody
Copy link
Contributor Author

Now that we have the release tarball, this might only be an issue for a static build with bootstrap. Anyway, since most users will build through spack or the release tarball, this is no longer high priority.

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

No branches or pull requests

1 participant