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

Shared Vs. Static Libraries #37

Open
knight-of-ni opened this issue Jul 6, 2016 · 0 comments
Open

Shared Vs. Static Libraries #37

knight-of-ni opened this issue Jul 6, 2016 · 0 comments
Labels

Comments

@knight-of-ni
Copy link
Contributor

The cmake build system has been tested successfully from-source on redhat and ubuntu distros.

Today I moved into a (rpm) package building environment and got the unexpected linker error:
../libgen/libgen.so: undefined reference to gConfig'`

This only occurs when attempting to build via the rpmbuild tool.

That is when I remembered the original autotools build system built static, instead of share libraries. Sure enough, changing the cmake files to build Static libraries allowed rpmbuild to successfully a package.

This issue is to remind myself to do two things:

  • Learn from @web2wire why we are using static libraries, and whether or not we plan to ever go with shared. I'm sure there is a reason, I'm just looking to understand what it is.
  • add the STATIC parameter to each add_library command. I'd like to get initial commit for cmake superbuild #29 merged before I do this to avoid a merge conflict.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant