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

path to include files

When I put #include <ctype.h> at the top of my source file, the compiler finds it. If I add #include <reg688.h>, I get error "can't open file 'reg688.h'".
If change it to read #include <philips\reg688.h>, it still can't find the file. And if I put the full path in ( <c:\keil\c51\inc\philips\reg688.h> ) it STILL CAN'T FIND the file. What is this stupid compiler looking for?

Parents
  • But I don't want to change the original project or source files.

    Then why are you doing it?

    So, I need to copy the source code to a new directory, create a new project file,

    Now, whatever gave you that strange idea? What does copying the project folder around have to do with creating a new project?

    There was a code segment that the consultant created that had to be added manually to the project file that I was missing.

    Aha. So the error was exactly where I told you to look, and that leads you to the conclusion that

    nor is it "the wrong way" to achieve my goal

    If the thought of ever buying a product based on such reasoning weren't so scary, that might even be funny.

Reply
  • But I don't want to change the original project or source files.

    Then why are you doing it?

    So, I need to copy the source code to a new directory, create a new project file,

    Now, whatever gave you that strange idea? What does copying the project folder around have to do with creating a new project?

    There was a code segment that the consultant created that had to be added manually to the project file that I was missing.

    Aha. So the error was exactly where I told you to look, and that leads you to the conclusion that

    nor is it "the wrong way" to achieve my goal

    If the thought of ever buying a product based on such reasoning weren't so scary, that might even be funny.

Children
No data