• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 360 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.

errors in building codec package

YongchaoDeng
Intellectual 965 points

I build viddec_copy in ti.sdo.ce.example.codecs followed sprued5bCodec Engine Server Integrator's User's Guide (Rev. B).pdf.

There are some errors in build.

*******************************************************

[root@dengyongchao viddec_copy]# ls
lib       package.bld  package.xs        viddec_copy_ti_priv.h
makefile  package.mak  viddec_copy.c     VIDDEC_COPY.xdc
package   package.xdc  viddec_copy_ti.h  VIDDEC_COPY.xs
[root@dengyongchao viddec_copy]# xdc
generating interfaces for package ti.sdo.ce.examples.codecs.viddec_copy (because package/package.xdc.inc is older than ) ...
    translating VIDDEC_COPY
"ti/sdo/ce/examples/codecs/viddec_copy/VIDDEC_COPY.xdc", line 49:  can't resolve name (ti.sdo.ce.video.IVIDDEC)
error:  compilation failed: parser failed
gmake: *** [package/package.xdc.inc] error 1

***********************************************************************

I modify makefile in viddec_copy as followed.

************************************************************************

# include the files that defines XDC package, paths and build rules
EXAMPLES_ROOTDIR := /mydocument/montavista/OMAPL137_arm_1_00_00_07/codec_engine_2_22/examples

 

  • 0
    TI__Genius 17205 points

    YongchaoDeng said:
    I build viddec_copy in ti.sdo.ce.example.codecs followed sprued5bCodec Engine Server Integrator's User's Guide (Rev. B).pdf.

    sprued5b recommends you build with "makefile", not "xdc".

    YongchaoDeng said:
    "ti/sdo/ce/examples/codecs/viddec_copy/VIDDEC_COPY.xdc", line 49:  can't resolve name (ti.sdo.ce.video.IVIDDEC)

    The issue is that the codec package [correctly] has a dependency on the Codec Engine packages (in this case, ti.sdo.ce.video).  But your XDCPATH doesn't include "/mydocument/montavista/OMAPL137_arm_1_00_00_07/codec_engine_2_22/packages", so ti.sdo.ce.video can't be found.  Since you're calling "xdc" yourself, it's your responsibility to set that on your XDCPATH.  If you instead use "gmake" to build using the "makefile" in that directory, XDCPATH will be set via .../codec_engine_2_22/examples/xdcpaths.mak and will include the appropriate .../codec_engine_2_22/packages directory.

    In short, you should be able to follow the instructions in codec_engine_2_22/examples/build_instructions.html - which describe using xdcpaths.mak via gmake to build.

    Chris

  • 0 in reply to Chris Ring
    Intellectual 965 points

    I have build codec_engine_2_22 followed codec_engine_2_22/example/build_instructions.html.But now i want to study xdais and codec package,i read sprued6cCodec Engine Algorithm Creator User's Guide (Rev. C).pdf and some about xdais files.I want to write my algorthm(fir,fft etc) on OMAPL137 and make it work with codec engine(universal).So i read sprued6cCodec Engine Algorithm Creator User's Guide (Rev. C).pdf、sprued5bCodec Engine Server Integrator's User's Guide (Rev. B).pdf and SPRUE67Codec Engine Application Developer User's Guide (Rev. D).pdf now.

    I build viddec_copy use make(in linux) not gmake in command line instead of xdc, no errors in the process. This correct? And how can i create a release package?

     

  • 0 in reply to YongchaoDeng
    Intellectual 475 points

    One trick I did figure out for Linux:  gmake is built and distributed in XDCtools (in bin).  (I.e., gmake is not just for Windows.)  It seems to behave very much like GNU make; can't tell if it's customized, but it is a known/fixed version.

    If your build steps aren't making everything you need, it may be that xdc needs to be run to generate (and/or complete) makefiles that will get gmake to build more stuff.

  • 0 in reply to Dirk Helgemo
    TI__Intellectual 1920 points

    It seems that your process should be ok. It appears you were able to build the release package with the help from Chris.

    However, if you are having any issues, I would first try using gmake as stated in the instructions.

    Also, the gmake versions installed in the xdctools folder is necessary for rebuilding DSPLINK. If you dont require this, the version of gmake on your host should be ok.