------- Comment From [email protected] 2016-04-07 04:34 EDT------- Due to the Easter break we had not been able until yesterday to internally discuss the topic, and we had all but ignored this defect - your asking one more time for info next time before closing a defect is highly appreciated. Thanks.
As to the outcomes of our discussion we found that: 1) In a development role a user would install 'libopencryptoki-dev' and be able to build and run an externally provided package (ok). 2) But how does 'distribution to production machines' work for open source packages using the package's bootstrap, configure, make process? When it comes to environments with a build machine and later distribution of packages to production machines (production machines without devel packages installed!) the build must occur using the soname of the libraries Simple example: gcc test_ock.c -g -O0 -o test_ock /usr/lib/opencryptoki/libopencryptoki.so.0 -ldl -I /root/opencryptoki/usr/include/pkcs11/ This might be well-documented and even well-known for Debian/Ubuntu systems - is there documentation about this? Please advise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561598 Title: Missing link to opencryptoki library by libopencryptoki0 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencryptoki/+bug/1561598/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
