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

problems after upgrade to mdk 4.10

I got a lot of errors after upgrade mdk 4.00 to mdk 4.10:

error: #5: cannot open source input file "stdio.h": No such file or directory
error: #5: cannot open source input file "cstddef": No such file or directory
error: #5: cannot open source input file "string.h": No such file or directory
error: #5: cannot open source input file "rt_sys.h": No such file or directory

What's wrong with mdk4.10? I use UV3, I'm not going to use UV4 until I don't know how to disable new awful appearance ;)

Parents
  • Yes, of course - you always have to specify the right path somehow!

    There are many ways to do it; eg,

    * In the Project properties - to apply to the whole Project;

    * In the Group properties - to apply to the whole Group;

    * In the File properties - to apply to an individual file.

    You can, of course, even put a fully-qualified path in the source code; eg,

    #include "C:/blah//Keil/blah/blah/includes/stuff.h"
    

Reply
  • Yes, of course - you always have to specify the right path somehow!

    There are many ways to do it; eg,

    * In the Project properties - to apply to the whole Project;

    * In the Group properties - to apply to the whole Group;

    * In the File properties - to apply to an individual file.

    You can, of course, even put a fully-qualified path in the source code; eg,

    #include "C:/blah//Keil/blah/blah/includes/stuff.h"
    

Children
  • And if you don't specify explicitly somehow in your Project and/or source, then the tools will use some default, which may or may not be what you need - especially if you've been installing and/or updating multiple versions...

    Getting the include paths right is a standard part of any porting exercise - including an update of the tool versions.

  • Yes, but the strange thing was that as far as I could tell, the file was located at the right place (but still it was required to specify an explicit location). Personally I never had such issues, as I always install MDK update on top of each other (thus, into the same root path).