• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 297 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.

finding libraries

Jonathan Mulvaine
Prodigy 110 points

Below I've pasted some of the errors from my console.  My question is about the process of finding the libraries I need to include.  How does one use the information from the console to find the correct libraries to include.  I fail to find references on the internet and I fail to find any TI documentation that helps solve this.  There has to be a good way to do this.

undefined first referenced
symbol in file
--------- ----------------
_H264VENC_TI_IDMA3 ./vivo_h264_x64P.obj
_H264VENC_TI_IH264VENC ./vivo_h264_x64P.obj
_LOG_printf4 C:\ti\dvsdk_1_10_00_26_DM648\codec_engine_1_20_02\packages\ti\sdo\ce\osal\lib\osal_bios.a64P<Log_BIOS.o64P>
_ti_sdo_ce_osal_LOG_Buffer ./vivo_h264_x64P.obj

  • 0
    TI__Guru* 84110 points

    Jonathan,

    Which device are you using?
    Which version of the Code Generation Tools are you using?
    Which version of CCS and BIOS are you using?
    What application are you trying to build and where did you get it from?

    In general, libraries should be mentioned in the documentation that goes with the application you are trying to build.

    It is likely that this question should be moved to the DM64x DaVinci Video Processor Forum, but we can wait until you supply a little more information.

    Regards,
    RandyP

  • 0 in reply to RandyP
    Prodigy 110 points

    DM648

    CCS5.2.1 and 

    C6000

    BIOS 5_42_00_07

    The code is modified from the h.264 video compression example.  It has been modified some in CCS3 before I have imported it to CCS5.
    I've reduced the dependency problems down to this unresolved symbol: _ti_sdo_ce_osal_LOG_Buffer

    I think you've basically answered my question though.  Documentation with the example should indicate which libraries are needed.  I still don't like the answer. 

  • 0 in reply to Jonathan Mulvaine
    Prodigy 110 points

    Perhaps this buffer is part of the code that would be auto-generated by tools.  I get the feeling it doesn't exist in a library.

  • 0 in reply to Jonathan Mulvaine
    TI__Guru* 84110 points

    Jonathan,

    You said the code was modified a few times. When was the last time that it compiled and linked without errors? What changes were made after that which led to the recent failures?

    It would be easy to say that the problem was in the porting of the application from CCS 3.1 to CCSv5.2.1. Did you change the version of BIOS along the way, too?

    You may need to verify that you have the exact same software packages and the exact same code generation and BIOS tools.

    Regards,
    RandyP