• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 1 reply
  • Subscribers 136 subscribers
  • Views 3540 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

why Mali_OpenCL_SDK_v1.1.0 use both static library and share library

yang

In Mali_OpenCL_SDK_v1.1.0

project libCommon compile to static library(./Common)

project libOpenCL compile to share library(./lib)

Parents
  • +1

    Hi yzl0208994,

    libOpenCL.so is a stub library to satisfy the cross compiler. You will be using the native libOpenCL.so library on the device you are targetting, hence why that is a shared library.

    libCommon.a can be either shared or static. We chose static in order to make it easier for deploying applications, as one binary instead of two.

    If you have issues with mixing shared and static, you can look at changing the SDK to build libCommon as shared, and make sure to deploy that .so along with your application to make it work.

    Kind Regards,

    Michael McGeagh

Reply
  • +1

    Hi yzl0208994,

    libOpenCL.so is a stub library to satisfy the cross compiler. You will be using the native libOpenCL.so library on the device you are targetting, hence why that is a shared library.

    libCommon.a can be either shared or static. We chose static in order to make it easier for deploying applications, as one binary instead of two.

    If you have issues with mixing shared and static, you can look at changing the SDK to build libCommon as shared, and make sure to deploy that .so along with your application to make it work.

    Kind Regards,

    Michael McGeagh

Children
No data