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
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.
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: