• State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 22 subscribers
  • Views 1616 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

#include in C51 retrieves wrong header file

Gary Lynch

I am designing a project using the Keil C51 V7.50 and
uVision 3 IDE V3.10a on a Silicon Labs C8051F046 MCU. My
project contains source file foo.c, which contains a
directive:

    #include "foo.h"

where foo.h contains standard header info and is located in
the same directory as foo.c.

When I run C51 from the command line, this module compiles
as I expect, but when I compile within uVision 3, it goes
out and finds another foo.h, located in another directory on
the same drive, which is not set up for this project, and
the compile fails.

I can find nothing in the documentation to explain this. I
have checked all the tabs in the "options" dialog box. When
I copy my correct foo.h into the alien directory, uVision 3
will compile it correctly, but I am not content to function
this way.

Any clues why this is happening?
============================================================
Gary Lynch            |     To send mail, change no$pam in
lynchg@no$pam.com     |     my domain name to stacoenergy

Parents
  • 0 in reply to Drew Davis

    Of course I'll sometimes reuse a file name. (Directories exist to allow hierarchical, compound file names.)

    In particular, I have a file with my favorite conventions for typedefs and such U8, U16, TRUE, etc), which has to be adapted to any particular compiler and processor. But this file always has the same name in different projects.

    I NEVER reuse a name. All project specific files start with 2 capital letters that identify the project. Files used across projects reside in a separate directory and do not have the preface to the filename.

    Erik

Reply
  • 0 in reply to Drew Davis

    Of course I'll sometimes reuse a file name. (Directories exist to allow hierarchical, compound file names.)

    In particular, I have a file with my favorite conventions for typedefs and such U8, U16, TRUE, etc), which has to be adapted to any particular compiler and processor. But this file always has the same name in different projects.

    I NEVER reuse a name. All project specific files start with 2 capital letters that identify the project. Files used across projects reside in a separate directory and do not have the preface to the filename.

    Erik

Children