Hi Ajay,
I think we have to classify the static-pre-compiled libraries.
For instance, if the static-pre-compiled library is a math library.
It just does some Mathematical Computing and doesn’t depend on
Other libraries. I think this math library can be link to
Unikraft. Another instance, if the static-pre-compiled library
depends on other libraries. You have to guarantee the dependent
libraries are in the Unikraft library pool.
In your case, the
/usr/lib/x86_64-linux-gnu/librt.a and /usr/lib/x86_64-linux-gnu/libpthread.a
would link to
libc.a to solve their link dependencies. But the
nolibc
In Unikraft is just a subset of
libc.a
Regards,
Wei Chen
Actually, my original query is how to link pre-compiled (static) libraries in unikraft?
but the libraries do not resolve linking problems.
Or am I understanding it incorrectly? Can pre-compiled static libraries be integrated/linked at all in unikraft?
On Wed, Apr 18, 2018 at 7:48 AM, Wei Chen <Wei.Chen@xxxxxxx> wrote:
But the
clock_gettime hasn’t been implemented in
nolibc or
libtime.
If your application just uses this function to print
timestampe, you
can implement a dummy function in your code in this time to pass the
linking.
--
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person,
use it for any purpose, or store or copy the information in any medium. Thank you.