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
Adding an external static library to Trusted Application #901
Comments
You'll find the interesting flags in |
Can you be a little more specific on how a static .a library can be linked to the object files after compilation? There are only cflags in $(TA_DEV_KIT_DIR)/mk/conf.mk but I'm looking for ld that can be set to a static library. Thanks |
perhaps try in ta_dev_kit.mk: libdirs += $(ta-dev-kit-dir)/lib Add your static library here and drop the library itself into the $(ta_dev_kit_dir)/lib. If it depends on any library such as libutils.a, make sure you add it before that. |
After adding
error. |
Try to recompile your static library with the compiler flags found in |
I managed to include the external library without having to link it to a TA. Since I already have the source code for the library, I didn't have to use the shared object of the library, I added all of the library's source code as part of the TA instead. |
Hi, I am trying to put the protobuf-c.a library into my Trusted Application. I tried this hackish way where I combined my static library with libutils.a. I also tried to add the static library independently by specifying it in ldargs-$(binary). However for both methods I got the following error:
I was wondering, if you can give me any pointers on how the static library for protobuf-c.a should be compiled or added to the build Makefile so the build for the TA works?
My make file currently looks like this:
The text was updated successfully, but these errors were encountered: