• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 887 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.

Understanding how to setup/install from scratch CCS and SDKs to create new and run older examples seamlessly

Mark Miliano
Intellectual 895 points

Other Parts Discussed in Thread: OMAP-L138

Hello,

After having worked with the 6748 EVM board and CCS 4.2 for a while I would really like to understand how to best setup/install from scratch all of the development tools so that when a new project is created, or examples are used- I do not get all kinds of linker errors. I have had this problem with every project I have created and have re-installed CCS, the BSP, NDK libraries over and and over to no avail- I am sure I am not installing things properly. I also looked at the system variables in windows XP to ensure they were set. But I have to say that the projects are always a huge hassle to deal with- and I am frustrated with manually finding every library and include file and adding them to my project (even ALL  the examples do this) every time. Any expert guidance on this matter would be extremely appreciated.

 Mark

  • 0
    TI__Guru*** 125430 points

    Please provide some examples of the types of errors you're seeing and I think we'll be able to better help.

    In general CCS will always need to know the locations and filenames for any libraries, header files, etc.  If the locations change then you will have to make updates.

  • 0 in reply to Brad Griffis
    Intellectual 895 points

    Hi Brad,

    appologies for the late reply I ended up reinstalling the entire CCS environment an it has taken me a while to get everything back to a bare install.

    I am looking for a generic method of setting up my system so it "sees" all include & library paths so that when I run an example or create a new project it will not ask for things like the following:

    **** Build of configuration Debug for project DSP eXp MMCSD Test ****

     

    C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake -k all 'Building file: ../src/main_mmcsd.c'

    'Invoking: Compiler'

    "C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/bin/cl6x" -mv6740 -g --include_path="C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/include" --include_path="C:/Documents and Settings/mark/My Documents/TI DSP workspace/DSP eXp MMCSD Test/inc" --include_path="" --diag_warning=225 --preproc_with_compile --preproc_dependency="src/main_mmcsd.pp" --obj_directory="src"  "../src/main_mmcsd.c"

    ERROR: option --include_path is missing its parameter 'dir'

     

    gmake: *** [src/main_mmcsd.obj] Error 1

    'Building file: ../src/test_mmcsd.c'

    'Invoking: Compiler'

    "C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/bin/cl6x" -mv6740 -g --include_path="C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/include" --include_path="C:/Documents and Settings/mark/My Documents/TI DSP workspace/DSP eXp MMCSD Test/inc" --include_path="" --diag_warning=225 --preproc_with_compile --preproc_dependency="src/test_mmcsd.pp" --obj_directory="src"  "../src/test_mmcsd.c"

    ERROR: option --include_path is missing its parameter 'dir'

     

    gmake: *** [src/test_mmcsd.obj] Error 1

    gmake: Target `all' not remade because of errors.

    Build complete for project DSP eXp MMCSD Test

    Thank you for the help,

    Mark

  • 0 in reply to Mark Miliano
    TI__Guru*** 125430 points

    Mark Miliano said:
    I am looking for a generic method of setting up my system so it "sees" all include & library paths

    There are a number of issues with setting up the compiler to "see everything".  In particular you will quickly start running into name space collisions, e.g. multiple header files with the same name, multiple libraries that define functions with the same name, etc.  For this reason it is the programmer's responsibility to tell the compiler which paths/libraries should be used an in which specific order.

     

    Mark Miliano said:

    C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake -k all 'Building file: ../src/main_mmcsd.c'

    'Invoking: Compiler'

    "C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/bin/cl6x" -mv6740 -g --include_path="C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/include" --include_path="C:/Documents and Settings/mark/My Documents/TI DSP workspace/DSP eXp MMCSD Test/inc" --include_path="" --diag_warning=225 --preproc_with_compile --preproc_dependency="src/main_mmcsd.pp" --obj_directory="src"  "../src/main_mmcsd.c"

    ERROR: option --include_path is missing its parameter 'dir'

    I put the erroneous part of the command line in red above.  It looks to me like the specific project you're using defines a variable and references that variable in the compiler include path.  Your project does not seem to have it defined. 

    Where did this project come from?  There are many ways of dealing with variables and portable projects so it would be helpful to know who created the project and which strategy they were using.  For example, is there a macros.ini file that goes along with this project?

    Mark Miliano said:
    I am looking for a generic method of setting up my system so it "sees" all include & library paths
  • 0 in reply to Brad Griffis
    Intellectual 895 points

    I am trying to compile the stock  C6748EXP_Test_MMCSD project from the Board Support Library of Logic PD's OMAP-L138 EVM board.  I am using the clean installation of CCS 4.2, with all of the updates to date.