RTSC package wizard - created successfully, but XDC release - errors

I see you are using dvsdk_2_00_00_22 which comes with mv_pro_5 tool-chain.  Did you install codesourcery toolchain separately?  I see many references trying to look for codesourcery tool chain....

Where did you tell the wizard to generate your package?  And where did you run 'xdc release' from?

It _looks_ like you're running 'xdc release' from within the XDC product, and as a result are trying to build some of the packages that are part of the XDC product(!), which isn't generally supported.  Attempting to do so may even be corrupting your XDC product installation.  :(

You should be creating your new package in a clean directory, and running the 'xdc release' step from that directory.

Chris

Hi Chris,

Thanks for your reply.

I am refering Wizard_instructions[1].pdf for generating the package.

From Wizard_instructions[1].pdf,

RTSC Codec Package Wizard: XDC Release

Following is the XML file generated:

We are running  "./xdc release -PR ."  from XDCtools

[satyam@localhost xdctools_3_10_05_61]$ ./xdc release -PR .

From Wizard instructions, as per the below instruction,i am not able to run the xdc release command from the base directory. I am getting the following error:

[satyam@localhost maf]$ xdc release –PR .

bash: xdc: command not found

[satyam@localhost maf] $ /home/satyam/dvsdk_2_00_00_22/dm6467_dvsdk_combos_2_05/packages/ms/cisco/codecs/maf

Kindly help us in resolving this issue.

Thanks & Regards,

Ayeesha

Hi Juan,

Thanks,  we have downloaded and installed codesourcery version- arm 2007q1-21 Release, We have modified the environment variables PATH and XDCPATH, with adding the bin folder path accordingly. and we are invoking the command xdc release -PR from the folder /home/satyam/dvsdk_2_00_00_22/xdctools_3_10_05_61 folder. we are still receiving the same error . (part of it i have pasted here)

making release: Wed Feb 17 12:22:53 IST 2010 ...
======== .interfaces [./packages/gnu/targets] ========
======== .interfaces [./packages/gnu/targets/arm] ========
======== .interfaces [./packages/gnu/targets/arm/rtsv5T] ========
======== .interfaces [./packages/gnu/targets/arm/rtsv6] ========
======== .interfaces [./packages/gnu/targets/codesourcery] ========
======== .interfaces [./packages/gnu/targets/codesourcery/rtsv5T] ========
making package.mak (because of package.bld) ...
Warning: gnu.targets.codesourcery targets are deprecated. Please use
gnu.targets.arm targets instead. See the documentation for gnu.targets.arm
and gnu.targets.codesourcery packages for more information.
js: "/home/satyam/dvsdk_2_00_00_22/xdctools_3_10_05_61/packages/gnu/targets/ITarget.xs", line 255: Error: /vendors/cs/arm/arm-2007q1//bin/arm-none-linux-gnueabi-gcc cannot be found. Ensure that rootDir for the GCArmv5T target is set correctly in ./config.bld
gmake[1]: *** Deleting file `package.mak'
======== .interfaces [./packages/gnu/targets/codesourcery/rtsv6] ========
making package.mak (because of package.bld) ...
Warning: gnu.targets.codesourcery targets are deprecated. Please use
gnu.targets.arm targets instead. See the documentation for gnu.targets.arm
and gnu.targets.codesourcery packages for more information.
js: "/home/satyam/dvsdk_2_00_00_22/xdctools_3_10_05_61/packages/gnu/targets/ITarget.xs", line 255: Error: /vendors/cs/arm/arm-2007q1//bin/arm-none-linux-gnueabi-gcc cannot be found. Ensure that rootDir for the GCArmv6 target is set correctly in ./config.bld

we are not sure whether the XDCPATH is set correctly.

Thanks & Regards,

Ayeesha

Let me investigate this with our internal teams.  I suspect that our current XDC build scripts may not have the proper support for codesourcery tool-chain.  It is certainly possible to add support for other tool-chains, but want to confirm if our DVSDK_2_00_00_22 software packages will work with codesourcery tool-chain or not.

[edit]: I missed Chri's response at the top; FYI, he is actually much more knowledgable than I in this area.

Uma Rao said:

From Wizard_instructions[1].pdf,

RTSC Codec Package Wizard: XDC Release

• After running the wizard, browse to “base” directory

of the output files

– E.g. If the package name is ti.sdo.codecs.mpeg2dec and the

output repository is /my_codec_repo, then change

directories to /my_codec_repo/ti/sdo/codecs/mpeg2dec

• Run “xdc release –PR .”

– Don’t forget the dot

I highlighted the key point above in red.  You must run 'xdc release -PR .' from _your_ created directory/repository, not within the xdc product.  If xdc is not your path, you should provide a full path to the xdc executable.  Something like

   > cd /my_codec_repo/ti/sdo/codecs/mpeg2dec
   > $(XDC_INSTALL_DIR)/xdc release -PR .

Your error is happening b/c you're running the xdc command from the XDC product directory - and as a result, you're [errantly] trying to build the XDC product's packages(!) - which isn't supported.  You _don't_ want to build the XDC product's packages, you want to build your new wizard-generated content.

Finally, the xdc command is documented here, if you're curious what the arguments do - or what _other_ options are available:

http://rtsc.eclipse.org/docs-tip/Command_-_xdc

Chris

Chris,

Thanks for your help and support. i went to the output repository and invoked xdc release -PR. i did not recieve any errors. i have pasted the output  of the same below

making release: Thu Feb 18 20:09:45 IST 2010 ...
======== .interfaces [.] ========
======== .interfaces [./ce] ========
.interfaces files complete: Thu Feb 18 20:09:46 IST 2010.
======== .libraries [.] ========
======== .libraries [./ce] ========
.libraries files complete: Thu Feb 18 20:09:46 IST 2010.
======== .dlls [.] ========
======== .dlls [./ce] ========
.dlls files complete: Thu Feb 18 20:09:46 IST 2010.
======== .executables [.] ========
======== .executables [./ce] ========
.executables files complete: Thu Feb 18 20:09:46 IST 2010.
======== release [.] ========
all files complete.
generating schema include file list ...
generating external package references package/package.ext.xml ...
generating package references graph package/package.rel.dot ...
making release file msat_cisco_vdec_vencdec.tar (because of package/rel/msat_cisco_vdec_vencdec.xdc.inc) ...
======== release [./ce] ========
all files complete.
generating schema include file list ...
generating external package references package/package.ext.xml ...
generating package references graph package/package.rel.dot ...
making release file msat_cisco_vdec_vencdec_ce.tar (because of package/rel/msat_cisco_vdec_vencdec_ce.xdc.inc) ...
release files complete: Thu Feb 18 20:10:02 IST 2010.

please let me know whether this is correct now

Thanks and Regards,

Ayeesha

Hi Juan and Chris,

Thanks for the help. I am able to create the Codec Package and Server Package successfully. I am now using the Qualiti tool for making it XDAIS Compliance,  The Codec package is failing the Qualiti tool test. Please find the details below of the same.

XDAIS Rules 8, 9, 10: Namespace compliance

Report: Failed

Test Description:

(Rule 8) All external definitions must be either API identifiers or API and vendor prefixed.

(Rule 9) All undefined references must refer either to the operations specified in Appendix B (a subset of C runtime support library functions and a subset of the DSP/BIOS HWI API functions), or TI's DSPLIB or IMGLIB functions or other XDAIS-compliant modules.

(Rule 10) All modules must follow the eXpressDSP naming conventions for those external declarations disclosed to the client.

Test Status Details:

Test failed. Problem: Not all global symbols defined by the module have the "VIDDEC_TI_" prefix (i.e. module_vendor_).

The following is the list of offending symbols:
viddec_copy__versionNumArray
viddec_copy__versionString
viddec_copy__whatString
I have attached the zip file containing the screen shot of Qualiti tool, with the test reports and the xml files created in RTSC Codec package creation.

Thanks,

Ayeesha