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

How to change compiling paths in makefile?

Oscar Herranz
Intellectual 770 points
Other Parts Discussed in Thread: OMAP3530

Hi guys!!

I am using the DSPLINK package (version 1.65) in order to communicate ARM & DSP in the beagleboard platform and CCSv5.1 like IDE (OS Linux). I am building the executables for DSP with the makefile provided for DSPLINK. I want to modify some includes of the project, but I do not know where I have to make it (CCS? ,makefile structure? dsplinkcfg written in perl). I have already built the dsplink module and I have modified the files of configuration of DSP (c64xxp_5.xx_linux.mk).

For instance, I have a builded project in CCSv5.1 with some defines and includes that I can see in the console of CCS. Where and how can I add more options? Options like more paths, more defines, whatever...One solution could be modifing perl file or modifing some parameter of some makefile structure of dsplink? Any suggestions?? Thanks in advance.

Regards

Óscar


  • 0
    TI__Mastermind 22760 points

    Oscar,

    Is your DSP executable based on one of the DSPLINK samples?  If so, you will have a file called COMPONENT, where you can set the variable, USR_CC_FLAGS, to include your search paths.  For example, if you look at the message sample, in the directory:

        dsplink/dsp/src/samples/message/DspBios

    you will find the COMPONENT file.  Set USR_CC_FLAGS to something like:

        USR_CC_FLAGS    := -I<your search path>

    Best regards,

        Janet

  • 0 in reply to janet
    Intellectual 770 points

    Great answer Janet!!

    So,I have more questions...

    For instance,the building console writes the result of DSP compilation (an extract) :

    Compiling swiMessage.c...
    /opt/TI/c6000/bin/cl6x -o3 -dMAX_DSPS=1 -dMAX_PROCESSORS=2 -dID_GPP=1 -dOMAP3530 -dPROC_COMPONENT -dPOOL_COMPONENT -dNOTIFY_COMPONENT -dMPCS_COMPONENT -dRINGIO_COMPONENT -dMPLIST_COMPONENT -dMSGQ_COMPONENT -dMSGQ_ZCPY_LINK -dCHNL_COMPONENT -dCHNL_ZCPY_LINK -dZCPY_LINK -dPROCID=0 -dOMAP3530 -dOMAP3530_INTERFACE=SHMEM_INTERFACE -dPHYINTERFACE=SHMEM_INTERFACE -dDSP_SWI_MODE -I/home/user/dsplink/dsp/inc -I/home/user/dsplink/dsp/inc/DspBios -I/home/user/dsplink/dsp/inc/DspBios/5.XX -I/home/user/dsplink/dsp/inc/DspBios/5.XX/OMAP3530 -I/home/user/dsplink/dsp/inc/OMAP3530 -I/home/user/dsplink/dsp/inc/C64XX -I/home/user/ServidorNFS/nfs02/workspaceCCSv5.1/DSP_Cproject -I/home/user/ServidorNFS/nfs02/workspaceCCSv5.1/DSP_Cproject/DspBios -I/home/user/ServidorNFS/nfs02/workspaceCCSv5.1/DSP_Cproject/DspBios/ -I/opt/TI/bios/packages/ti/bios/include -I/opt/TI/c6000/include -I/opt/TI/bios/packages/ti/rtdx/include/c6000 -I/opt/TI/bios/packages/ti/psl/include -I/home/user/dsplink/dsp/BUILD/OMAP3530_0/INCLUDE -q -pdr -pdv -pden -ml3 -mv6400+ --disable:sploop    -d"TSK_MODE" -fr"/home/user/dsplink/dsp/BUILD/OMAP3530_0/MESSAGE_DSP/OBJ/RELEASE" swiMessage.c

    The paths -I (underlined) that executes the program above are default. How can I modify this paths? Your answer is excellent in order to add more paths, but I do not know where have to go for that. Does it belong to makefile structure?

    The builded application is a example of dsplink, so that it has the same structure, but the app is in other folder independently to the dsplink package(basically, I have copied the needed files in other place and I have changed some files, for instance, the COMPONENT file)

    Thanks in advance

    Óscar

  • 0 in reply to Oscar Herranz
    TI__Mastermind 22760 points

    Oscar,

    In your case then, can you just build your example without the DSPLink Makefile and just use a CCS project?  You need to add the DSPLink dsp/inc to your include path and link in the DSPLink dsp library.  I haven't actually tried this, but it seems like it should be the easiest approach.

    Best regards,

        Janet