• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 305 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.

xdcpaths.mak

darren robinson
Prodigy 250 points

Good day.

Below is a paste of my  codec_engine_2_26_02_11/examples/ xdcpaths.mak file.  I am struggling to complete modifying.  I am working with DVSDK 4_02_00_06 on the dm365 evm and the Tool-chain is  CodeSourcery G++ Lite.

It seems that there is no option / or variables for me to add the paths to the Tool-chain I am using and seems to only mention MontaVista toolchain, which I thought is no longer used with this release of the SDK.

Could you please show me how I should update this file correctly.  So that I can build examples etc.   Thanks.  Darren.


# (Mandatory) specify correct compiler paths and names for the architectures
# you'll be building for:

# compiler path and name for Montavista Arm 9 toolchain. NOTE: make sure the
# directory you specify has a "bin" subdirectory
CGTOOLS_V5T := /db/toolsrc/library/tools/vendors/cs/arm/arm-2007q3
CC_V5T := bin/arm-none-linux-gnueabi-gcc
CGTARGET := gnu.targets.arm.GCArmv5T

# compiler path and name for uClibc toolchain. NOTE: make sure the
# directory you specify has a "bin" subdirectory
CGTOOLS_UCARM9 := /db/toolsrc/library/tools/vendors/opensource/buildroot/10122007/build_arm/staging_dir/usr
CC_UCARM9 := bin/arm-linux-gcc

# WinCE toolchain.
#WINCE_ROOTDIR := C:/WINCE600
#WINCE_PROJECTROOT := $(WINCE_ROOTDIR)/_your_ProjectRoot_/Wince600/TI_EVM_3530_ARMV4I

# compiler path and name for TI C64x toolchain. NOTE: make sure the
# directory you specify has a "bin" subdirectory
#CGTOOLS_C64P := /db/toolsrc/library/tools/vendors/ti/c6x/6.0.16/Linux
#CC_C64P      := bin/cl6x

# compiler path and name for TI C674 toolchain. NOTE: make sure the
# directory you specify has a "bin" subdirectory
#CGTOOLS_C674 := /db/toolsrc/library/tools/vendors/ti/c6x/6.1.5/Linux
#CC_C674      := bin/cl6x

# compiler path and name for Linux 86 toolchain. NOTE: make sure the
# directory you specify has a "bin" subdirectory
#CGTOOLS_LINUX86 := _your_Linux86_installation_directory
#CC_LINUX86   := bin/gcc

# -----------------------------------------------------------------------------

  • 0
    TI__Expert 3265 points

    Hi Darren,

    Are you following the build instructions under  codec_engine_3_22_01_06\examples\build_instructions.html ?

    You need to set the CGTOOLS_V5T and CGTOOLS_UCARM9 properly based on your install path for the code gen tools. You should be able to use CodeSorcery G++ once your path and other settings are correct as per the build instructions.

    By the way, the setting you have above refer to the path "/db/toolsrc/library/tools/vendors/...", which is not to match your build environment. Point to your own installation's codegen tool path.

    Best regards,

    Murat

     

  • 0 in reply to raormanrat
    Prodigy 250 points

    Hi Murat

     

    I was following the buld instructions under codec_engine_2_26_02_11.  Since on the codec engine download page, in red, is a comment which says, codec_engine 3.x is intended for DSP/BIOS 6 users and most DVSK users should continue to use CE 2.x releases. 

    The path /db/toolsrc/.....  was originally found there when I opened the file to edit, as explained in the build instructions.   However, I am unsure how to locate the code gen tools for my environment.

    Thanks and Regards

    Darren

     

  • 0 in reply to darren robinson
    TI__Expert 3265 points

    darren robinson said:

    Hi Murat

     

    I was following the buld instructions under codec_engine_2_26_02_11.  Since on the codec engine download page, in red, is a comment which says, codec_engine 3.x is intended for DSP/BIOS 6 users and most DVSK users should continue to use CE 2.x releases. 

    The path /db/toolsrc/.....  was originally found there when I opened the file to edit, as explained in the build instructions.   However, I am unsure how to locate the code gen tools for my environment.

    Thanks and Regards

    Darren

     

    Hi Darren,

    You would need to install the CodeSourcery Lite codegen tools and set up the path according to your own installation's path.

    Perhaps following topics regarding how to set up a software development environment for EZSDK might be helpful:

    http://processors.wiki.ti.com/index.php/DM814x_EZ_5.03_Software_Developers_Guide

    http://processors.wiki.ti.com/index.php/Installing_CodeSourcery_Lite

    Murat