-
Notifications
You must be signed in to change notification settings - Fork 9
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
1479: lib: Don't force fcontext to be STATIC lib #1481
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #1481 +/- ##
===========================================
- Coverage 83.00% 82.82% -0.18%
===========================================
Files 783 765 -18
Lines 29505 28879 -626
===========================================
- Hits 24490 23920 -570
+ Misses 5015 4959 -56
|
Please manually check that the resulting dynamic library builds, links, and loads happily on nvcc, since that's where this came up. |
Builds fine with both Just a note, that UPDATE: Failing tests seem to be unrelated to nvcc or shared libs. I'm getting same errors on Ubuntu 20 with clang-10. Weird UPDATE_2: Memory footprint issues are not present when building with Unity, not sure why (this also explains why we don't face these issues on our CI, where we have both clang3.9 and gcc-6 with fcontext and Unity) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me, is that everything?
6f72a7d
to
d8d9dcc
Compare
Fixes #1479
Without specified lib type, it will default to
STATIC
, but withBUILD_SHARED_LIBS
set to ON, it will be built asSHARED
.