Closed damb closed 2 years ago
I test it under Debian 11 and got same linking error
Again, thanks for reporting @morealaz.
Most probably, I simply forgot to link the library where it would have been required. As a workaround enabling SQLite support globally (i.e. when configuring the SeisComP build) should work as well.
I'll look into into it and will come back.
Does #115 solve the linking issue on your side?
As a workaround enabling SQLite support globally (i.e. when configuring the SeisComP build) should work as well.
I did this and it worked but test_scdetect_cc_integration
test failed.
Does #115 solve the linking issue on your side?
It worked but Without enabling SQLite support globally, 7 test failed, including
with enabling SQLite support globally only test_scdetect_cc_integration
test failed.
AFAIU, running SeisComP tests for some modules (e.g. fdsnws
) requires to enable SQLite3 support globally.
test_scdetect_cc_integration
tests: could you please open another issue with more details? Particularly, I'm interested in the output of the commandctest -V -R '^test_scdetect_cc.*'
executed from within the build
directory.
AFAIU, running SeisComP tests for some modules (e.g.
fdsnws
) requires to enable SQLite3 support globally.
Probably that explain other failed tests
Does Link against libsqlite3 #115 solve the linking issue on your side, as well (i.e. without enabling SQLite support globally)? (I tested on archlinx, already, though it would be good to have the confirmation from your side, as well.)
Yes it fixed linking issue.
Regarding the failing
test_scdetect_cc_integration
tests: could you please open another issue with more details? Particularly, I'm interested in the output of the commandctest -V -R '^test_scdetect_cc.*'
executed from within the
build
directory.
Ok, I've done it in #116 .
The continuation from #112.