• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 295 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP3530 DSPLink GPP side library

Almohanad Fayez
Intellectual 510 points

Hi I was wondering if there's a way to generate a shared library from the DSPLink example projects instead of static libraries,  it seems that the COMP_TYPE=LIB flag in the COMPNENT file only generates static libraries but I REALLY want shared ones .. thanks in advance

  • 0
    TI__Expert 4930 points

    Fayez,

    The DSPLink build system does not have support to generate shared library. It only generates static libraries.

    However, you can update the build system to generate a so instead of a lib. This will require updating the build system, testing it etc. Would that help?

    Deepali

  • 0 in reply to Deepali Uppal
    Intellectual 510 points

    Deepali,

     

    yes it would be EXTREMELY helpful.  I'm currently working on wrapping dsplink applications (in library form) for python, essentially targetting the DSP from python.  I'm currently using SWIG to perform the C++ DSPlink library wrapping for python.  In such scenarios static libraries can cause alot of issues since different modules can end up with different copes of the same library ... so multiple copies of POOL and PROC calls which would of course be a bad thing.

     

    For now I managed to to hack th mk files, basically doing the same calls that are made for LIB which generates the *.a and I make calls to make a shared library in the same manner that i would do for a regular shared library.  When I used readelf to confirm that the library is in fact shared readelf agreed that it's shared ... am i safe to assume that this is all i needed to do?

    thanks

  • 0 in reply to Almohanad Fayez
    TI__Expert 4930 points

    Hello

    If you could share the exact changes to the build system, I can communicate further on the validity of the changes

    Deepali

  • 0 in reply to Deepali Uppal
    Intellectual 510 points

    I was having problems generating the sonames from the library i generated within the DSPLINK environment.  I ended up taking the *.o from the compile process and used openembedded to generate a shared library.  For a hack it seems to be running reasonably well.  When I have time I plan to look more closely into generting it through the DSPLINK tools unless TI at that point supports that natively through its tools.

    The only potential problem I can think of when using the DSPLINK tools to generate the library, is linking against the library in OpenEmbedded because it will need a local copy installed in the build environment for compiling and linking against programs which will make use of the  library.