-
Notifications
You must be signed in to change notification settings - Fork 284
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
Fails to build with STRICT_ABI option #1262
Comments
Labeling it as high since it supposedly hinders packaging of toxcore, as @yangf, who opened the #1261 issue, is the package maintainer of libtoxcore in Debian. |
So it looks like the solution is to make building testing/* optional,
and have STRICT_ABI imply building neither these nor the autotests?
|
I think so, yes. autotests (the automated test suite) and regular test (the testing programs) are linked against the toxcore and both call into toxcore's internals. When toxcore is built with Of course there are other ways to work around this rather than disabling building of autotests and tests, like always statically compiling toxcore into the autotests and tests -- this is actually what tox-bootstrapd does. I think disabling building of tests is an acceptable solution, not to mention we wanted to be able to disable tests for a while now, so |
While investigating #1261 I have found that toxcore doesn't compile with a
STRICT_ABI
cmake option due to test binaries not being able to find internal ABI symbols when linking against the shared toxcore.Output
We got a new cmake flag
AUTOTEST
in master which can be used to disable autotests, but even then the build fails due to regulat test programs still being enabled:The text was updated successfully, but these errors were encountered: