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

Problem finding include files... should I set DosRun.bat variables?

James Thorton
Expert 1390 points

Hello, I have a problem long ago with header files. For example, I have the following file:

 

/*  ============================================================================
 *   Copyright (c) Texas Instruments Inc 2002, 2003, 2004, 2005                
 *                                                                             
 *   Use of this software is controlled by the terms and conditions found in the
 *   license agreement under which this software has been supplied.            
 *   ===========================================================================
 */
/** ============================================================================
 *   @file  csl_types.h
 *
 *   @path  $(CSLPATH)\inc
 *
 *   @desc  This file contains type definitions of data types for CSL
 *  ============================================================================
 */
#ifndef _CSL_TYPES_H_
#define _CSL_TYPES_H_

#ifdef __cplusplus
extern "C" {
#endif

#include <ti/sdo/pspdrivers/soc/dm6437/dsp/tistdtypes.h>

....

.

 

       And the CCS is saying me that it does not find the <ti/sdo/pspdrivers/soc/dm6437/dsp/tistdtypes.h> file. I use to solve going to build options and adding the folder where is this file in the preprocessor directive for EVERY file that had the problem (I tried to do it globally but did not always work). So I would like to know how to solve this conflict in a easier and better way. I have seen that the environment variables are set in DosRun.bat, but I do not know what DIR I should add. And in general terms for this kind of problems where I could find some info about header and environment variables?

 

Thanks in advance

  • 0
    TI__Mastermind 41665 points

    It seems my C:\dvsdk_1_01_00_15\psp_1_00_02_00\pspdrivers\soc\dm6437\dsp\inc\csl_types.h starts off a bit different, it does not have the path in front of the tistdtypes.h include, just "#include <tistdtypes.h>", so it is possible you are using the wrong version of the csl_types.h file.

    In general for building the examples in the DM6437 DVSDK you just have to set the C:\dvsdk_1_01_00_15\xdcpaths.mak so it has the proper paths to the various libraries and header files. You may also set some Windows environment variables to make some builds simpler but I do not think you need any for the CSL, I don't seem to have any paths related to CSL in my environment variables.

  • 0 in reply to Bernie Thompson TI
    Expert 1390 points

    Hello, thanks a lot. But... fool question: how could add the .mak file in my project properly in order to my program see all the header files?

     

  • 0 in reply to James Thorton
    TI__Mastermind 41665 points

    The xdcpaths.mak file is only for the projects that are using rtsc/xdc to build, primarily the demo and examples that utilize codecs where it would already be included, it would not be added in a normal project.

    Assuming you are working with a normal project here you can add additional paths for CCS to find the header files in Project -> Build Options... -> Compiler Tab -> Preprocessor Category -> Include Search Path (-i) box, simply add in the paths to any directories containing the header files you are missing seperated by semicolons.

    The one catch here is that if your header file has that long path built into the #include statement, than you have to have the project build options pointing to the base directory of where the rest of the path in the #include statement can be found (i.e. if you have #include </fruit/apple/grannysmith.h> in your header file than you put C:/include/food; in the build options and not C:/include/food/fruit/apple;), which is why my first thought on this is that you are using some odd version of the csl header file, I am not sure you should have that extra path in the #include statement (mine does not).