• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 648 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 importing CCSv3.3 Projects into CCSv4.2

DSPfilterer
Prodigy 110 points


I have a couple programs that were written in CCSv3.3 that I'm trying to get to run in CCSv4.2.  They build, compile and run in 3.3 but when I imported them to 4.2 using 'Import Legacy CCSv3.3 Project' and tried to build one I get the error:

 fatal error #5:

could not open source file "std.h"

#include <std.h>

I've tried everything I can think of, including doing a search on the computer for all the files named 'std.h' and including their individual paths to the 'include options' for the project.  At this point I'm at a loss as to what 4.2 is wanting me to do.

  • 0
    Prodigy 110 points

    Also, this error occurs multiple times.  Pretty much every time a source file attempts to include the 'std.h' this error comes up.  Right now I have around 10 of this same error all from different .c files that are attempting to open it.

  • 0 in reply to DSPfilterer
    TI__Guru**** 473961 points

    Hello,

    Is this a DSP/BIOS project?

    ki

  • 0 in reply to Ki
    Prodigy 110 points

    Hi,

    No, the particular project that I am attempting to build does not use BIOS.

    Ellen

     

    Also there is another error generated:

    fatal error #5:

    could not open source file "log.h"

    Where the file trying to open 'log.h' is another header file rather than a .c.

  • 0 in reply to DSPfilterer
    TI__Guru**** 171349 points

    Ellen,

    Both include files are part of the DSP/BIOS package (check its include directory at <CCS_INSTALL_DIR>\bios_5_41_10_36\packages\ti\bios\include)

    The fact they are included in a non-BIOS project may be because they are leftovers from other projects that used these files - I did this myself many times.

    For example, the <std.h> contains several typedefs for SmInt, LgUns, etc. and were usually used across BIOS and non-BIOS files.

    The <log.h>, though is used exclusively by BIOS to define LOG functions (LOG_printf, LOG_error, etc.)

    Usually including the include directory above in the compiler search path solves the issue, but for non-BIOS projects I strongly recommend using the types defined by the compiler in the include file <stdint.h>.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 110 points

    Rafael,

    It does indeed allow me to build the project.  I have about 50 warnings now, but no errors.

    Thanks!

    Ellen