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.

importing VLIB or any libraries from Tı to my project

Hello and thanks for the help.

I have dm6446 sysytem and my development tools are installed on ubuntu host pc. I run eclipse as an IDE and my project on eclipse is build with the help of make files generated according to the XDC tools. So my dsp side algorithms are first compiled then i think the linker converts the compiled files to a dsp library file which is something.a64P . Now i want to use VLIB functions call by my DSP routines. I think i have to package my "vlib.l64p" file according to the xdc standarts and use it accordingly. Please warn me if I am wrong. If this is the case then what should i have to do? I have created package.bld and package.xdc files and do the coding,for the path requirements.But i m not sure that this is the point required.May be i donot have to put in package my library file?

Serdar

  • Serdar,

    There are two different methods available to include your vlib.l64p in the final DSP executable(.a64P).

    In the first method, you have to create a standard RTSC package for your library with package.xdc, Module.xdc,package.xs etc. Then build this RTSC package using XDC tools and later include this package xdc.useModule('mycompany.organisation.type.vlib.VLIB) in your build config file;This method is recommended if your library is compatible with xDAIS and xDM standard.

    In the alternative method, you can simply link the lib vlib.l64p along with your build.

    Create a file link.cmd inside your build directory and include the line

    -l vlib.l64p.

    Now add the following line 

    lopts: "-l link.cmd",

    in your dsp executable build file package.bld.

    For ex

    Pkg.addExecutable("Hellod", targ, plat, {
            cfgScript:    "Hello",   
            profile:    "profile",  
            lopts: "-l link.cmd", /* To include the link.cmd in the build*/
            test:    testOpts,   
        });       

    For details about the lopts option, please refer to

    xdctools_directory/packages/xdc/bld/Executable.xdc:

    xdctoold_dire/examples/basic/profile/package.bld

     

    Regards

    Ansari

     

     

     

  • Ansari,

    Thanks for the reply. I have never tried to use linker options.After your answer i tried to create a file called link.cmd at the folder containing my DSP side codes. Then i tried to "addExecutable" lines but actually i do not know what should be in the "cfgscript" and "profile" files. And i tried with a dummy names(not related with any file) but when i try to build project, of course , XDC tools check for the cfg script file which is not existing.

    So i need to write a cfgscript file but i do not know how to write it.

    Serdar  

  • Serdar,
    what are you trying to build? It seems you have VLIB library (vlib.l64p) and a DSP library (something.a64P). Now, you are building an app that uses these libraries, and you are doing it in a Standard Make Project, right?
    In package.bld you are supposed to specify the build parameters for the executable by calling addExecutable().

    The only required parameters for addExecutable are its name, the target and the platform. For example, 
    Pkg.addExecutable("Hello", targ, targ.platform);
    builds an executable "Hello", for the target specified earlier in package.bld, and for the default platform for that target. Do you already have package.bld that specifies the target and a file config.bld that configures targets?

    If you are not familiar with these files and their purpose you may want to check this link http://rtsc.eclipse.org/docs-tip/RTSC_Packaging_Primer#TOC and more specifically this lesson: http://rtsc.eclipse.org/docs-tip/RTSC_Packaging_Primer/Lesson_5.

    Please let me know if I am guessing correctly your setup, and if not can you give us more details about what you are building and how?

  • Serdar,

    My assumption is , you have built a DSP library file lib1.a64P using XDC tools. There is another library vlib.l64p

    Now you want to call some functions in vlip.l64p from the built library lib1.a64P

    While building the library lib1.a64P, it is enough if you provide the header file path in your lib1 build setup.

    Please provide the details about the usage of your library lib1.a64P.

    If you are going to use your library lib1.a64P in some application which is also XDC built, then you need to use the either of following methods (recommended by me in the earlier thread).

    Either make a simple RTSC package for the library vlib.l64p, build the RTSC package  and include them in your app.cfg file as follows

    xdc.useModule('mycompany.organisation.type.vlib.VLIB)

    or just include the library path vlib.l64P via linker command file.

    Please let me know your DVSDK version details, so that I can provide the relevant examples

     

  • where i would get vlib.l64p?
  • Can you post your question to the device forum (e.g. e2e.ti.com/.../439 They will know more about vlib.

    Todd