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

How are .h files treated in a uVision2 project?

Hello,

For me, it's still not clear why the include files (.h) are treated in such a cumbersome way in the uVision2 Project philosophy. When you have a project and you create a group -for instance- called 'Header files' then you have to specify that those files are Text documents to be able to add it to your project. The file types in the file open dialog box do not contain something separate for .h files, whereas this is the case for e.g. .c, .a* and .src files. Could someone explain me why is this?
Wouldn't it be more logic, user-friendly and convenient if the .h-files would be treated the same way as .c- or .a51-files?

Rgds,

Geert

Parents Reply Children
No data