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

Can't open source file xdc/std.h

Helmut Forren
Mastermind 6805 points

I get the error 'could not open source file "xdc/std.h"'.

I read http://e2e.ti.com/support/embedded/f/355/p/43513/151951.aspx?PageIndex=1 and now I'M EVEN MORE CONFUSED!  That post is clear as mud to me!

Can someone please help me figure this out?  Here's what I did:

1) Using CCS version 4.1.1.00014.

2) Found vidanalytics_copy example project on dvsdk.

3) Created <Higher Level Path>\Codecs folder

4) Created examples folder within that

5) Copied vidanalytics_copy folder from dvsdk to <Higher Level Path>\Codecs\examples

6) Ran CCS and selected <Higher Level Path>\Codecs as workspace

7) Selected CCS's Project / Import Legacy CCCSv3.3 Project.

8) Navigated to <Higher Level Path>\Codecs\examples\vidanalytics_copy\pjt and pointed to vidanalytics_copy.pjt

9) Import ran with no error messages.  Note it did NOT create a migration.log file.

10) Now see <Higher Level Path>\Codecs\vidanalytics_copy

11) NOTICE STUPID ECLIPSE BEHAVIOR: new project has source code files from example, but it only linked to those examples rather than making copies of <Higher Level Path>\Codecs\examples\vidanalytics_copy\*.c over to <Higher Level Path>\Codecs\vidanalytics_copy\*.c

12) QUESTION: Is there a way to get source code files copied from example?  I simply DELETED source code from project, then manually copied files, then added to project.  NOTE THAT I HAD xdc/std.h ERROR PRIOR TO DOING THIS, SO THIS STEP DID NOT INTRODUCE PROBLEM.

13) Did Rebuild All and got error 'could not open source file "xdc/std.h"'.  I have no clue how to check for cygwin or how to provide -D or -C switches to program.  Please help!

Thanks very much,

Helmut

  • 0
    TI__Genius 17205 points

    This might help:

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

    It seems you're building a library (as opposed to linking an executable), so you can ignore all the linker.cmd/compiler.opt business in the thread you referenced - those files are only generated when configuring/linking an executable.

    Assuming you're on a C64P device, you should be able to add -Dxdc_target_name__=C64P and -I $(XDC_INSTALL_DIR)/packages to your CCS project.

    Chris

  • 0 in reply to Chris Ring
    Mastermind 6805 points

    Thx.  Where in CCS do I Add those defines?  I find CCS very poorly organized, in both UI and doc, so having never defined such things for it before, I have no clue how to do it!

    Thanks again,

    Helmut

  • 0 in reply to Helmut Forren
    Mastermind 6805 points

    Also, I find in advance I have no XDC_INSTALL_DIR environmental variable.  I do have an XDCROOT and I guess I'll substitute it.

    EDIT: I just found <project>, right click, build properties, C6000 compiler, predefined symbols AND ALSO Include Options.  Trying it now...

  • 0 in reply to Helmut Forren
    Mastermind 6805 points

    "EDIT" above fixed the xdc/std.h problem but left a new one.

    Now it can't find "ti/xdais/dm/ividanalytics.h".  However, in the project panel tree under the project, under Includes, is a folder named

    "c:\Program Files\Texas Instruments\xdais_6_25_01_08\packages\ti\xdais"

    Below the tree is a "dm" and within that a ividanalytics.h.  Checking the hard disk, that full path does exist:

    "c:\Program Files\Texas Instruments\xdais_6_25_01_08\packages\ti\xdais\dm\ividanalytics.h"

    So I would think the file should be found.  Is it perhaps some kind of "where this ends and that begins" problem with the path?  That is, should the include read "dm/ividanalytics.h" instead of "ti/xdais/dm/ividanalytics.h"?

  • 0 in reply to Helmut Forren
    Mastermind 6805 points

    Yep.  I find that the Include folders under the project panel tree indeed come from the build properties setting.  In addition to the existing 

    "c:\Program Files\Texas Instruments\xdais_6_25_01_08\packages\ti\xdais"

    include I added one that ended in a different place on the path:

    "c:\Program Files\Texas Instruments\xdais_6_25_01_08\packages"

    I kept both, just in case.

    This fixed the problem.  Indeed, the include "ti/xdais/dm/ividanalytics.h" has to pick up from "...\packages" that I added, as opposed to magically figuring out "ti\xdais" was duplicated.  This DOES make sense.

    Anyway, between the fix suggested by Chris and fixing this inconsistency, I can now build with success.

    Thanks very much,

    Helmut